Document revision date: 15 July 2002 | |
Previous | Contents | Index |
All LAN devices are characterized by a collection of parameters. The parameters define the operational characteristics of a LAN device on the medium to which the device is connected.
To set LAN device parameters directly, enter the SET DEVICE command at the LANCP> prompt. The LANCP utility issues this command to the LANACP server process, which then issues the appropriate QIOs to set the driver characteristics.
The syntax for the SET DEVICE command is:
SET DEVICE device-name [/qualifiers] |
Table 24-9 provides a brief description of the SET DEVICE command qualifiers that apply directly to LAN devices.
Qualifier | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
/AGING_TIMER= value | Sets the amount of time in seconds to age source routing cache entries before marking them stale. | ||||||||
/ALL | Sets data for all LAN devices. | ||||||||
/ATMADDRESS=LES++ |
Sets the LAN emulation server (LES) address for asynchronous transfer
mode (ATM). Usually the address is not user specified, and this
qualifier is used only if you want a specific address. By default the
address is determined by software from the configuration server for the
LES.
The /ATMADDRESS=LES qualifier's syntax is as follows:
|
||||||||
/ATMADDRESS=ARP++ |
Sets the address resolution protocol (ARP) server address for Classical
IP over ATM. This qualifier is required before a LIS is enabled if the
local host is not the ARP server.
The /ATMADDRESS=ARP qualifier's syntax is as follows:
|
||||||||
/AUTONEGOTIATE (default)
/NOAUTONEGOTIATE |
Enables or disables the use of auto-negotiation to determine the link settings. You may need to disable link auto-negotiation when connected to a switch or device that does not support auto-negotiation. | ||||||||
/CACHE_ENTRIES= value | Sets the number of entries to reserve for caching source routing address entries. | ||||||||
/CLIP++ |
Sets up the Classical Internet Protocol (CLIP) over ATM (RFC1577). The
CLIP qualifier implements a data-link level device as a client and/or a
server in a logical IP subnet (LIS). This allows the IP protocol to
transmit Ethernet frames over the ATM network. The /CLIP = ENABLE
command causes the the system to join the LIS. The /CLIP = DISABLE
command causes the client to leave the logical IP subnet.
Note that a LIS requires a server, and there must be only one server for each subnet. Communication between subnets can only be performed by a router. There can only be one client for each ATM adapter. The /CLIP qualifier's syntax with standard Internet dotted notation
is as follows:
The meanings of the syntax for /CLIP are as follows:
Keywords and their meanings for /CLIP are as follows:
|
||||||||
/CONTENDER
/NOCONTENDER |
Specifies that the Token Ring device is to participate in the Monitor Contention process when it joins the ring. The /NOCONTENDER qualifier directs the device not to challenge the current ring server. | ||||||||
/DEVICE_SPECIFIC=
FUNCTION="xxxx", VALUE=n |
Allows some device-specific parameters to be adjusted.
The following list shows the commands and their meanings. FUNCTION="CCOU"---Clears all device and driver counters. If the value is supplied, it is ignored. |
||||||||
/DISCOVERY_TIMER= value | Sets the number of seconds to wait for a reply from a remote node when performing the source routing route discovery process. | ||||||||
/DLL=( enable-option, exclusive-option, size-option, knownclientsonly-option) |
Provides the MOP downline load service settings for the device.
In this qualifier, you can specify:
|
||||||||
/EARLY | Enables Early Token Release on the device. | ||||||||
/ELAN++ |
Sets LAN emulation. The /ELAN qualifier has two values: enable and
disable. With /ELAN=ENABLE with the keyword STARTUP, the LAN emulation
is loaded when LANACP starts. With /ELAN=DISABLE, the same parameters
as ENABLE can be used.
The /ELAN qualifier's syntax is as follows:
The meaning of the syntax for /ELAN are as follows:
Keywords and their meanings for /ELAN are as follows:
|
||||||||
/FULL_DUPLEX
/NOFULL_DUPLEX |
Enables full-duplex operation of a LAN device. Before full-duplex
operation results from the use of this qualifier, additional device or
network hardware setup may be required. Some devices may be enabled for
full-duplex operation by default. Some devices may not allow the
setting to be changed.
The /NOFULL_DUPLEX qualifier disables full-duplex operations. |
||||||||
/JUMBO
/NOJUMBO (default) |
Enables the use of jumbo frames on a LAN device. Only the Gigabit Ethernet NICs support jumbo frames. | ||||||||
/MAP=(MULTICAST_ADDRESS=address,
FUNCTIONAL_ADDRESS=address) |
Defines a functional address mapping entry. | ||||||||
/MAX_BUFFERS= value | Sets the maximum number of receive buffers to be allocated and used by the LAN driver for the LAN device. | ||||||||
/MEDIA= value |
|
||||||||
/MIN_BUFFERS= value | Sets the minimum number of receive buffers to be allocated and used by the LAN driver for the LAN device. | ||||||||
/PERMANENT_DATABASE (SET command only) | Updates the device entries in the LAN volatile device database with any data currently set in the permanent database. | ||||||||
/PVC=(vci[,...])++ |
Defines the permanent virtual circuit (PVC). This is an optional
qualifier.
A list of PVCs is defined for use by CLIP clients. This command should be used before enabling the CLIP client. PVC has to be setup manually in the ATM switch. The vci is the VCI (Virtual Circuit ID) of the PVC. |
||||||||
/NOPVC=(vci[,...])++ | Does not set the permanent virtual circuit (PVC). | ||||||||
/RING_PURGER++ | Enables the ring purging process of the FDDI device. | ||||||||
/SOURCE_ROUTING++ | Enables source routing on the Token Ring device. | ||||||||
/SPEED= value | Sets the speed of the LAN, if multiple speeds are supported. | ||||||||
/SR_ENTRY=(LAN_ADDRESS=
address,
RI= routing-information) |
Statically defines a specific source-routed route for a specific node. | ||||||||
/TOKEN_ROTATION++ | Sets the requested token rotation time for the FDDI ring. | ||||||||
/TOKEN_TIMEOUT++ | Sets the restricted token timeout time for the FDDI ring. | ||||||||
/TRANSMIT_TIMEOUT++ | Sets the valid transmission time for the FDDI device. | ||||||||
/UPDATE | Adds LAN devices that are not currently in one of the LAN device databases to that database. The DEFINE DEVICE command applies to the permanent database; the SET DEVICE command applies to the volatile database. | ||||||||
/VOLATILE_DATABASE (DEFINE command only) | Updates the device entries in the LAN permanent device database with any data currently set in the volatile database. |
LANCP> SET DEVICE/CONTENDER/MEDIA=UTP/NOEARLY/SOURCE ICA0 |
LANCP> SET DEVICE/MEDIA=TWIST EWB0 |
LANCP> SET DEVICE/ALL/MIN_BUFFERS=12 |
LANCP> DEFINE DEVICE EXA0/MOPDLL=(ENABLE,EXCLUSIVE) |
LANCP> DEFINE DEVICE/ALL/MOPDLL=NOEXCLUSIVE |
LANCP> SET DEVICE EXA0/MOPDLL=(ENABLE,NOEXCLUSIVE) LANCP> SET DEVICE FXA0/MOPDLL=(ENABLE,EXCL,KNOWN) |
The LAN volatile and permanent device databases contain a single entry for each LAN device that exists on the system. Each entry in the LAN volatile device database contains device information and MOP downline load counters information. Each entry in the LAN permanent device database contains device information that is used to populate the volatile database when the LANACP LAN server process is started.
Typically, each database contains the same devices. However, the permanent database may contain entries for devices that have not yet been configured or installed in the system. The LANACP LAN server process maintains the volatile device database. The LANCP utility maintains the permanent device database. You can manipulate either database using the LANCP utility commands depending on your user privileges, as follows:
The following sections describe how to enter and remove devices from
the LAN permanent and volatile device databases, and how to enable and
disable MOP downline load services.
24.6.1 Displaying Devices in the LAN Device Databases
To display information in the LAN permanent device database, enter the LIST DEVICE command using the following syntax:
LIST DEVICE device-name [/qualifiers] |
To display information in the LAN volatile device database, enter the SHOW DEVICE command using the following syntax:
SHOW DEVICE device-name [/qualifiers] |
Table 24-10 provides a brief description of the LIST DEVICE and SHOW DEVICE qualifiers.
Qualifier | Description |
---|---|
/ALL | Lists, or shows all devices which match device names. |
/CHARACTERISTICS | Same as the /PARAMETER qualifier. |
/COUNTERS+ | Displays device counters. |
/DLL | Lists or shows downline load characteristics. |
/MAP | Displays the current configuration of the functional address mapping table. |
/MOPDLL | Same as DLL. |
/OUTPUT= file-name | Creates the specified file and directs output to it. |
/PARAMETERS | Displays status and related information about the device. |
/REVISION+ | Displays the current firmware revision of the adapter, if available or applicable. |
/SR_ENTRY | Displays the contents of the current source routing cache table. |
If you do not specify a qualifier, the utility displays the matching devices without additional information. |
To enter a device into the LAN permanent device database or to modify an existing entry, enter the DEFINE DEVICE command using the following syntax:
DEFINE DEVICE device-name [/qualifiers] |
To enter a device into the LAN volatile device database or to modify an existing entry, enter the SET DEVICE command using the following syntax:
SET DEVICE device-name [/qualifiers] |
24.6.3 Deleting Devices from the LAN Device Databases
To delete a device from the LAN permanent device database, enter the PURGE DEVICE command using the following syntax:
PURGE DEVICE device-name [/ALL] |
To delete a device from the LAN volatile device database, enter the CLEAR DEVICE command using the following syntax:
CLEAR DEVICE device-name [/ALL] |
For the PURGE DEVICE and CLEAR DEVICE commands, the /ALL qualifier deletes all LAN devices in the LAN permanent device database.
LANCP> PURGE DEVICE/ALL |
LANCP> CLEAR DEVICE EXA0 |
The LAN volatile and permanent node databases contain a single entry for each defined LAN node. Each entry in the LAN volatile node database contains node information and MOP downline load counters information. Each entry in the LAN permanent node database contains node information that is used to populate the volatile database when the LANACP LAN server process is started.
Typically, each database contains the same nodes. The LANACP LAN server process maintains the volatile node database. The LANCP utility maintains the permanent node database. You can manipulate either database using the LANCP utility commands depending on your user privileges, as follows:
The following sections describe how to enter nodes into and remove nodes from the LAN permanent and volatile node databases.
Previous | Next | Contents | Index |
privacy and legal statement | ||
6017PRO_098.HTML |