LANCP Volatile Device Database
The volatile device database is a database that contains information about LAN devices that exist on the system. The database contains a single entry for each LAN device that exists on the system; each entry contains device information and MOP downline load counters information.
The LANCP volatile device database is populated with information from the permanent device database when the LANACP LAN server process is started. Therefore modifications to the volatile database are only valid until the LAN server process is restarted. To make sure the modifications survive a restart of the server, modify the permanent device database.
Viewing the Database
To view the volatile device database, use the LANCP SHOW DEVICE command. (To view the permanent database, use the LANCP LIST DEVICE command; these commands share the same qualifiers).
|SHOW DEVICE/CHARACTERISTICS||Displays status and related information about the device||
Example of LANCP SHOW DEVICE/CHARACTERISTICS
LANCP> show dev ewa0 /characteristics SMAN43 Device Characteristics EWA0 (13-MAR-2019 09:04:18.23): Value Characteristic ----- -------------- 1500 Device buffer size Normal Controller mode External Internal loopback mode 00-22-64-94-BC-6F Default MAC address (Hardware LAN address) Multicast address list Ethernet Communication medium FF-FF-FF-FF-FF-FF MAC address (Current LAN address) 128 Minimum receive buffers 256 Maximum receive buffers Yes Full duplex enable Yes Full duplex operational 00-22-64-94-BC-6F MAC address (Current LAN address) TwistedPair Line media type 1000 Line speed (mbps) Enabled Auto-negotiation Enabled Flow control Disabled Jumbo frames 0 Failover priority Link Up Link state
|SHOW DEVICE/COUNTERS||Displays device counters.||
Example of LANCP SHOW DEVICE/COUNTERS
LANCP> show dev ewa0 /counters SMAN43 Device Counters EWA0 (13-MAR-2019 09:04:35.02): Value Counter ----- ------- 582896 Seconds since last zeroed 62788872086 Bytes received 625542635 Bytes sent 46698021 Packets received 7090058 Packets sent 317308984 Multicast bytes received 43771772 Multicast bytes sent 2842575 Multicast packets received 453952 Multicast packets sent 0 Unrecognized unicast destination packets 971437 Unrecognized multicast destination packets 0 Unavailable station buffers 0 Unavailable user buffers 0 Alignment errors 0 Frame check errors 0 Frame size errors 0 Frame status errors 0 Frame length errors 0 Frame too long errors 0 Data overruns 0 Send data length errors 0 Receive data length errors 0 Transmit underrun errors 0 Transmit failures 0 Carrier check failures 0 Station failures 0 Initially deferred packets sent 0 Single collision packets sent 0 Multiple collision packets sent 0 Excessive collisions 0 Late collisions 0 Collision detect check failures 1 Link up transitions (6-MAR-2019 15:09:40.00) 0 Link down transitions None Time of last generic transmit error None Time of last generic receive error
|SHOW DEVICE/CLEAR_COUNTERS||Clears device counters and internal driver counters after a SHOW DEVICE/COUNTERS or SHOW DEVICE/INTERNAL_COUNTERS command. Subsequent SHOW commands show the counter values accumulated since the clear was done. This affects counters displayed by LANCP only.|
|SHOW DEVICE/RESTORE_COUNTERS||Restores device counters and internal driver counters prior to a SHOW DEVICE/COUNTERS or SHOW DEVICE/INTERNAL_COUNTERS command.|
|SHOW DEVICE/DLL or SHOW DEVICE/MOPDLL||Displays LAN volatile device database information related to MOP downline load for the device.||
Example of LANCP SHOW DEVICE/DLL
LANCP> show dev ewa0 /dll SMAN43 Device Listing, volatile database (13-MAR-2019 09:08:00.12): --- Downline Load Service Characteristics --- Device State Access Mode Clients Data Size ------ ----- ----------- ------- --------- EWA0 Disabled NoExclusive NoKnownClientsOnly 246 bytes
|SHOW DEVICE/INTERNAL_COUNTERS||Displays internal counters. By default, it does not display zero counters. To see all counters, including zero, use the addition qualifier /ZERO. To see the debug counters, use the additional qualifier /DEBUG.||
Example of LANCP SHOW DEVICE/INTERNAL_COUNTERS
LANCP> show dev ewa0 /internal_counters SMAN43 Device Internal Counters EWA0 (13-MAR-2019 09:08:16.08): Value Counter ----- ------- --- Internal Driver Counters --- "Merl5704" Device name "Jul 27 2016 10:18:07" Driver timestamp 100 Driver version (X-n) 21000000 Device revision (Broadcom 5701,5703,5704,5715 chip) 47829521 Device interrupts 1 Link transitions 583118 Link checks 1 Device resets 1 Device initializations 388705 User start/change/stop requests 320 Standard receive buffers 8 Jumbo receive buffers (current) 8 Jumbo receive buffers (minimum) 8 Jumbo receive buffer allocations 2158 Standard buffer size (bytes) 1518 Standard packet size (bytes)(device standard ring) 9658 Jumbo buffer size (bytes) 9018 Jumbo packet size (bytes)(device jumbo ring)) 000002A4 Requested link state <FlowControl, Fdx, 1000 mb, Auto-negotiation> 000002A5 Current link state <FlowControl, Fdx, 1000 mb, Auto-negotiation, Link up> 00000003 Remote flow capabilities <Transmit_Pause, Receive_Pause> 4 Current link up timer 00040488 Driver flags <Device_Link_Handling, Dynamic_Interrupt_Coalescing, 5704, Copper> 00000008 Driver state <RunUp> 64 DMA width (bits) 66 BUS speed (mhz) PCI-X BUS type IOSAPIC Interrupt mode 00000086 MSI control (Alloc<6:4>,Req<3:1>,Enable<0>) 16 Transmit coalesce value 16 Receive coalesce value 50 Transmit interrupt delay (usec) 10 Receive interrupt delay (usec) 100 DIM (dynamic interrupt mitigation) tics 18 DIM receive interrupts 19 DIM receives done 10 DIM transmit interrupts 18 DIM transmits done 5920 Map registers allocated 0:00:01.00 Transmit time limit 0:00:00.25 Timer routine interval --- Registers (wrote/read) --- 210002B8 210000BA Misc Host Control 00E04F08 00E04F08 MAC Mode <Enable_FHDE, Enable_RDE, Enable_TDE, Enable_TX_Stats, Enable_RX_Stats, Link_Polarity, Max_Deferral, TX_Burst, PM1> 0F40141C 00800003 MAC Status <Signal_Detect, PCS_Synched> 00001006 00001006 RX Mode <ExtendedHash, FlowCtrl, Enable> FFFFFFFF 00000008 TX Status <LinkUP> --- Time Stamps --- 161:58:48.03 Current uptime 0:00:08.19 Last reset 0:00:11.94 Last link up 161:58:36.09 Total link uptime 0:00:11.94 Total link downtime 0:00:02.00 Shortest link uptime period acceptable 0:00:10.00 Link uptime period to nullify blocking 0:01:00.00 Maximum time to block a link check --- Driver Auto-Negotiation Context (fiber) --- Not_Autoneg Current state --- Fork Delay (after scheduled) --- 7384 10..19 milliseconds --- Transmit Time --- 18255 10..19 milliseconds 1 20..29 milliseconds --- Receive completion time --- 7879 10..19 milliseconds --- One second timer time --- 30 10..19 milliseconds 1 20..29 milliseconds 12 30..39 milliseconds 12 40..49 milliseconds 2 50..59 milliseconds 1 100..109 milliseconds 1 >150 milliseconds --- Status Block --- 00000060 Status tag value 00000005 Status <Updated> 273 Receive Standard Consumer index 785 Receive Ring 0 Producer index 509 Send Ring 0 Consumer index --- Statistics Block --- ----- Statistics - Receive MAC --- 62789143368 Bytes received 43856648 Unicast packets received 1788916 Multicast packets received 1054724 Broadcast packets received 1165783 Packets (64 bytes) 122524 Packets (65-127 bytes) 4475574 Packets (128-255 bytes) 43337 Packets (256-511 bytes) 1075 Packets (512-1023 bytes) 40891995 Packets (1024-1522 bytes) ----- Statistics - Transmit MAC --- 679551923 Bytes sent 6637276 Unicast packets sent 259772 Multicast packets sent 194355 Broadcast packets sent ----- Statistics - Receive List Placement State Machine --- 46700288 Frames received onto return ring 1 425 Receive threshold hit ----- Statistics - Send Data Initiator State Machine --- 7091403 Frames sent from send ring 1 ----- Statistics - Host Coalescing State Machine --- 7120513 Send producer index updates 48729929 Ring status updates 48347695 Interrupts generated 382234 Interrupts avoided 3 Send threshold hit --- Driver Messages --- 6-MAR-2019 14:09:39.30 Link up: 1000 mbit, full duplex, flow control (txrx) 6-MAR-2019 14:09:35.67 Device type is BCM5704C (UTP) Rev B0 (21000000) 6-MAR-2019 14:09:35.55 Merl5704 located in 64-bit, 66-mhz PCI-X slot 6-MAR-2019 14:09:35.55 Auto-negotiation mode assumed set by console
|SHOW DEVICE/MESSAGES||Displays the console messages displayed by the LAN driver as part of the LAN driver internal counters. This qualifier is included for convenience, to avoid scanning the internal counters to get to the message data.||
Example of LANCP SHOW DEVICE/MESSAGES
LANCP> show dev ewa0 /messages SMAN43 Device Internal Counters EWA0 (13-MAR-2019 09:09:11.67): Value Counter ----- ------- 6-MAR-2019 14:09:39.30 Link up: 1000 mbit, full duplex, flow control (txrx) 6-MAR-2019 14:09:35.67 Device type is BCM5704C (UTP) Rev B0 (21000000) 6-MAR-2019 14:09:35.55 Merl5704 located in 64-bit, 66-mhz PCI-X slot 6-MAR-2019 14:09:35.55 Auto-negotiation mode assumed set by console
|SHOW DEVICE/REVISION||Displays the current LAN driver and device revision information if available or applicable. Not all LAN drivers maintain revision information.||
Example of LANCP SHOW DEVICE/REVISION
LANCP> show dev ewa0 /revision SMAN43 Device Revisions EWA0 (13-MAR-2019 09:09:31.89): Value Component ----- --------- 00000000 Device hardware revision 08400100 00000001 Port driver revision 08410208 00000001 LAN common routines revision
|SHOW DEVICE/TRACE||Displays LAN driver trace data.||
Example of LANCP SHOW DEVICE/TRACE
LANCP> show dev ewa0 /trace SMAN43 Device Trace Data EWA0 (13-MAR-2019 09:10:28.68): Trace mask 00E427F0,FFFFFFFF, stop mask 00000000,00000000, trace buffer size 256 entries 00000001,0 = One-second timer 00000002,0 = Interrupt 00000004,0 = Fork process started 00000008,0 = Fork process done 00000010,0 = Fork error 00000020,0 = Fork soft error 00000040,0 = State change 00000080,0 = First user startup 00000100,0 = User start/change/stop 00000200,0 = Last user stop 00000400,0 = Device shutdown 00000800,0 = Receive issued 00001000,0 = Receive done 00002000,0 = Receive error 00004000,0 = Receive packet 00008000,0 = Transmit issued 00010000,0 = Transmit queued 00020000,0 = Transmit done 00040000,0 = Transmit error 00080000,0 = Transmit packet 00100000,0 = DMA segment 00200000,0 = SR entry 00400000,0 = VCI action 00800000,0 = LAN common 01000000,0 = LAN other 02000000,0 = RDL error 0,00000001 = Link state 0,00000002 = Transmit timeout 0,00000004 = Stopped machine 0,00000008 = Reset device 0,00000010 = Init device, part 1 0,00000020 = Init device, part 2 0,00000040 = Check state machines 0,00000080 = Auto-negotiation 0,00000100 = Setup link 0,00000200 = Check link 0,00000400 = Check link error 0,00000800 = Force link settings 0,00001000 = Apply link settings 0,00002000 = Apply flow settings 0,00004000 = Enable loopback 0,00008000 = Write PHY 0,00010000 = Read PHY 0,00020000 = SET_MAC function 0,00040000 = Message 0,00080000 = Long fork time 0,00100000 = Long transmit time 0,00200000 = Link down avoided 0,00400000 = ISR receive refill 0,00800000 = Long complete rcv 0,01000000 = Rcv return bug 0,02000000 = Xmt ring bug 0,04000000 = DIM adjustment 0,08000000 = Receive error pkt 0,10000000 = Long second 0,20000000 = Link flap/bounce 0,40000000 = Other Sequence # EntryTimeStamp Delta Time Description XmtOut RcvOut Misc AddlData ---------- -------------- ----- ---- ----------- ------ ------ ---- -------- 4082272 583319.269735 0 08:09:53.74 LAN common 0 72 01 STCU 85EEFF00 4082273 583319.269736 1 08:09:53.74 LAN common 0 72 01 SCLS 8EAFA000 85EEFF0 0 00000004 4082274 583319.269737 1 08:09:53.74 User start/change/stop 0 255 18 85EEFF00 000002A5 0148014 8 01400008 4082275 583319.269738 0 08:09:53.74 Check state machines 0 255 18 00000001 4082276 583319.269785 47 08:09:53.74 Check state machines 0 255 18 00000002 4082277 583319.269812 26 08:09:53.74 LAN common 0 72 01 PCHI 00003123 4082278 583319.269812 0 08:09:53.74 LAN common 0 72 01 PCHE 00003103 4082279 583319.344642 74829| 08:09:53.81 Check link 0 255 08 040002A5 0000796D 0000000 1 000002A4 4082280 583320.344689 1000046% 08:09:54.81 Check link 1 255 08 040002A5 0000796D 0000000 1 000002A4 4082281 583321.344643 999954# 08:09:55.81 Check link 1 255 08 040002A5 0000796D 0000000 1 000002A4 <...>
|SHOW DEVICE/VLAN||Displays a list of IEEE 802.1Q tags that are configured on the switch port connected to the specified physical LAN device. LANCP listens for the GVRP packets that contain the configuration information and displays the configured tags. The switch periodically sends GVRP (GARP VLAN Registration Protocol) (GARP = Generic Attribute Registration Protocol) packets to provide VLAN configuration information in compliance with the IEEE 802.1Q specification. If GVRP is not configured on the switch, or if the LAN device is not connected to a switch, this command displays only the list of tags that the VLAN drive has configured.||
Example of LANCP SHOW DEVICE/VLAN
LANCP> show dev ewa0 /vlan SMAN43 Listening for VLAN configuration data on device EWA0 (13-MAR-2019 09:11:10.74) ........ SMAN43 VLAN configuration visible on device EWA0 (13-MAR-2019 09:11:24.74): No VLANs found
Changing the Database
To add a device to the volatile device database or modify an entry for a device there, use the SET DEVICE command (for the permanent database, use the DEFINE DEVICE command; these commands share the same qualifiers).
|SET DEVICE/ALL||Sets data for all LAN devices. If you specify a device name, all matching LAN devices are selected.|
|Allows some device-specific parameters to be adjusted. These are useful for debug purposes or for experiments while doing performance measurements. Like other LANCP commands which affect devices, this command requires SYSPRV privilege. Specify the negated qualifer to clear all device-specific parameter data. These functions are described in a text file on the system, SYS$HELP:LAN_COUNTERS_AND_FUNCTIONS.TXT.|
|SET DEVICE/DLL or SET DEVICE/MOPDLL=(enable-option, exclusive-option, size-option, knownclientsonly-option)
/DLL and /MOPDLL values
Specify ENABLE or DISABLE to indicate that MOP downline load service should be enabled or disabled for the device. Specify EXCLUSIVE to indicate that no other provider of MOP downline load service is allowed on the specified LAN device at the same time as LANACP. Specify NOEXCLUSIVE to indicate that the LAN MOP downline load service can coexist with other implementations (in particular, the DECnet Phase IV and DECnet Plus implementations that include MOP support). Note that when you select NOEXCLUSIVE, LANACP responds only to MOP downline load requests directed to nodes defined in the LAN node database. Use SIZE=value to specify the size in bytes of the file data portion of each downline load message. The permitted range is 246 to 1482 bytes. The default value is 246 bytes, which should allow any client to load properly. Note that some clients may not support the larger size. The recommended size for better load performance and less server overhead is the largest size that results in successful loads of all clients. The 1482 value is derived from the maximum packet size for CSMA/CD (Ethernet) of 1518 bytes less the 802e header and CRC (26 bytes) and MOP protocol overhead (10 bytes). You can override the size on a per-node basis. See Help on the LANCP SET NODE commands for details. Specify KNOWNCLIENTSONLY to indicate that MOP downline load requests should be serviced only for clients defined in the LAN permanent node database. When you select NOKNOWNCLIENTSONLY, LANACP searches the LAN$DLL directory for any images requested by clients that are not defined in the LAN node database. Note that this option is not available when NOEXCLUSIVE mode has been selected. When NOEXCLUSIVE mode is selected, LANACP services MOP downline load requests only for clients defined in the LAN node database.
|Provides the MOP downline load service settings for the device. Note that defaults apply to creation of an entry in the device database. If an existing entry is being modified, fields not specified remain unchanged.|
|SET DEVICE/MAX_BUFFERS=value||Sets the maximum number of receive buffers to be allocated and used by the LAN driver for the LAN device.|
|SET DEVICE/MIN_BUFFERS=value||Sets the minimum number of receive buffers to be allocated and used by the LAN driver for the LAN device.|
|SET DEVICE/PERMANENT||Updates the device entries in the LAN volatile device database with any data currently set in the permanent database. This allows you to update the volatile database after changing data in the permanent database, rather than repeating the commands for each updated entry to apply the changes to the volatile database.|
|SET DEVICE/TAG=value||Specifies the IEEE 802.1Q tag for the VLAN device. value is the IEEE 802.IQ tag number.|
Use SIZE=value to specify the size of the trace buffer in entries, each 32 bytes. The default is 2048 entries. The permitted range is 256 to 1000000. The size MOD 3 encodes the amount of packet data to include, either 35 bytes, 66 bytes, 97 bytes, or the entire packet. Use MASK=(value1,value2) to specify the trace mask to select which type of entries should be collected in the trace buffer. The first 32 bits consist of events common to most LAN drivers. The second 32 bits consist of events specific to the LAN driver for the specified device. Use STOP=(value1,value2) to specify the trace mask to select which type of entries should stop tracing. When a trace entry is made that matches one of the bits in the stop mask, the trace mask is cleared so that you can look at the trace data accumulated so far.
|Provides the LAN driver trace settings for the device. By default, most LAN drivers do tracing of error conditions and state changes. Tracing is controlled by an event mask that selects the events to trace, a stop mask that specifies when to stop tracing, and the size of the trace buffer.
You can change tracing settings at any time. The LAN driver allocates the trace buffer from non-paged pool. You can calculate the amount of pool needed by multiplying the number of entries by the size of each entry, 32-bytes. The impact of tracing on the system is negligible for error and state change events, more significant when all events are selected, and very significant when full packet tracing is enabled. The command SHOW DEVICE/TRACE displays trace results as well as the trace mask.
|SET DEVICE/UPDATE||Adds LAN devices that are not currently in the LAN volatile device database to that database. The initial entry for the device uses default values for all parameters. To update the volatile database with current information from the permanent database, use the SET DEVICE command with the /PERMANENT
qualifier. You can combine the /UPDATE and /PERMANENT qualifiers in a single SET DEVICE command.
|Specifies the physical LAN device that is to host the VLAN device. The /NOVLAN_DEVICE qualifier requests deactivation of the VLAN device. When deactivating the VLAN device, the device-name is not required because the VLAN driver knows which device is hosting the VLAN device. Note that a VLAN device cannot be deactivated if any applications continue to use the device.|
|SET DEVICE/AUTONEGOTIATE (default)
|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 support auto negotiation.|
|SET DEVICE/FLOW_CONTROL (default)
|Enables flow control on a LAN device.|
|SET DEVICE/FULL_DUPLEX (default)
|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 operation.
|SET DEVICE/JUMBO (default)
|Enables the use of jumbo frames on a LAN device. Only Gigabit Ethernet NICs support jumbo frames.|
Acceptable values are AUI (10Base2, 10Base5), TWISTEDPAIR (10BaseT), and AUTOSENSE (reperform the limited autosense algorithm). The default value is AUTOSENSE.
|Selects the cable connection. Normally, the selection is made during device initialization using a limited autosensing algorithm that selects twisted pair, but fails over to AUI (Attachment Unit Interface) if twisted pair does not appear to be functional. Thereafter, a cabling change would require a reboot of the system to take effect. This command allows you to change the selection without rebooting.
Some devices, such as the DE435, require a jumper change on the Ethernet card to switch between 10Base2 and 10Base5 (thinwire and thickwire). Other devices, such as the DE434, DE436, and DE500, have only twisted pair connections.
Valid values are 10, 100, 1000, 10000, or autonegotiate; the last choice, autonegotiate, selects the 10 Mb/s for Ethernet, 100 Mb/s for Fast Ethernet, 1000 Mb/s for Gigabit Ethernet, and 10000 Mb/s for 10-Gigabit Ethernet. If you select autonegotiate, the LAN driver repeats autonegotiation.
|Sets the speed of the LAN.|
|LAN Failover Devices|
|SET DEVICE/DISABLE||Disables the devices in a LAN Failover set. When disabled, LAN devices can be added to or deleted from the Failover set.|
|SET DEVICE/ENABLE||Enables a Failover set, which activates the Logical LAN device. The LAN Failover driver selects a LAN device from the LAN Failover set as the active device and then allows I/O to the Logical LAN device.|
|Specifies the members of a LAN Failover set.|
|SET DEVICE/PRIORITY=value||Sets the failover priority of a LAN device. Priority is given to the LAN failover device with the highest priority when choosing the active LAN device. When a LAN device with a higher priority becomes available, a failover transition to the newly available device is performed. This allows a system manager to set a preferred device by setting one LAN device to a higher priority than others. The LAN failover driver uses the preferred device when it is available.|
STANDARD is the Ethernet maximum packet size of 1519 bytes. JUMBO is the oversize packet size available with the Gigabit Ethernet devices. It is allowed only if all the LAN devices in the LAN failover set are Gigabit devices.
|Sets the packet size of the LAN failover device. Note that the size specified for the LAN failover device overrides the size set on
the members of the LAN failover set; that is, the JUMBO frame setting of a LAN device is of no consequence when the size is determined for the LAN failover device.
|SET DEVICE/SWITCH||Forces a LAN failover to another member of the LAN failover set. You can test LAN failover operation by using this command to switch from one device to another.|
|SET DEVICE/RING_PURGER||Enables the ring purger process of the FDDI device.|
|SET DEVICE/TOKEN_ROTATOR||Sets the requested token rotation time for the FDDI ring.|
|SET DEVICE/TOKEN_TIMEOUT||Sets the restricted token timeout time for the FDDI ring.|
|SET DEVICE/TRANSMIT_TIMEOUT||Sets the valid transmission time for the FDDI device.|
|Token Ring Devices|
|SET DEVICE/AGING_TIMER=value||Sets the amount of time in seconds to age Token Ring source routing cache entries before marking them stale. This timer expires when no traffic is sent to or received from the remote node in this amount of time. The default value is 60 seconds.
Increase this value when idle connections bounce between the stale and known states. Setting this value too low may cause unnecessary explorer traffic to traverse the LAN.
|SET DEVICE/CACHE_ENTRIES||Sets the number of entries to reserve for caching Token Ring source routing address entries. The default value is 200 entries. If your system directly communicates to a large number of systems, you may want to increase this number.|
|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.|
|SET DEVICE/DISCOVERY_TIMER=value||Sets the number of seconds to wait for a reply from a remote node when performing the source Token Ring routing route discovery process. The default value is 2 seconds.
If you have nodes that respond slowly on your extended LAN, you may need to increase this number to reduce the amount of explorer traffic that traverses your LAN.
|SET DEVICE/EARLY (default)
|Enables Early Token Release on the device. The /NOEARLY qualifier, disables Early Token Release.|
|SET DEVICE/MAP=(MULTICAST_ADDRESS=address, FUNCTIONAL_ADDRESS=address)
|Maps a standard multicast address to a functional address. Token ring devices do not support IEEE 802 standard globally defined group addresses. They do support functional addresses. A functional address is a locally administered group address that has 31 possible values. Each functional address sets one bit in the third through sixth byte of the address and bytes 1 and 2 are 03-00 (C0:00
in bit reversed format). The /NOMAP=(MULTICAST_ADDRESS=address) qualifier, clears the mapping established for the specified address.
|SET DEVICE/MEDIA=value||Selects the type of cable media used to connect the adapter to the Token Ring Media Access Unit (MAU) for devices that do not automatically detect this. Acceptable values for this are either unshielded twisted pair (UTP) or shielded twisted pair (STP). The default value is STP.|
|SET DEVICE/SOURCE_ROUTING (default) /NOSOURCE_ROUTING||Enables source routing on the Token Ring device. If you only have one ring in your LAN or you use transparent bridging, use the /NOSOURCE_ROUTING qualifier to turn off source routing.|
|SET DEVICE/SPEED=value||Sets the speed of the Token Ring LAN. Valid values are either 4 or 16, indicating 4 megabits per second or 16 megabits per second. The default value for Token Ring is 16, unless the LAN adapter supports a nonvolatile mechanism for setting this parameter.|
|SET DEVICE/SR_ENTRY=(LAN_ADDRESS=address, RI=routing-information)
|Statically defines a specific source-routed route for a specific node. The default value is no routes specified. This caching remains valid while used or until the aging timer expires.
Use this qualifier only as a last resort when isolating communication failures on extended LAN topologies. The /NOSR_ENTRY=(LAN_ADDRESS=address) qualifier, clears the previously defined static source routed route. The address is a standard 6-byte LAN address (given as hexadecimal byte characters separated by hyphens), which specifies the canonical form of the address. Using a colon as the separator character indicates the bit-reversed form of the address. The routing-information is the source routing field, specified as a series of two-byte hexadecimal characters (each byte separated by a hyphen). The field consists of a two-byte routing control field followed by up to 14 two-byte segment identifiers, each containing the ring number and the bridge number used in the hop. See Default Functional Address Mapping for Token Ring Devices.
|SET DEVICE/ATMADDRESS=LES=([NO]LES=the ATM server)||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.|
|SET DEVICE/ARP=(ARP=atm_arp_server)||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.|
|SET DEVICE/CLIP||Sets 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 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 syntax is as follows:
SET DEVICE/CLIP =(ip_subnet=a.b.c.d, ! IP address of the CLIP client ip_address=a.b.c.d, ! the subnet mask of the CLIP client parent=devnam, ! the parent device name name="ip subnet name", ! name for the LIS tp aid in operations and ! diagnostics enable, disable ! joins or leaves the subnet type = client|server) ! starts up a classical IP server and client
|SET DEVICE/ELAN||The /ELAN qualifier has two values: enable and disable. With /ELAN=ENABLE along with the keyword STARTUP, the LAN emulation is loaded when LANACP starts. With /ELAN=DISABLE, the same parameters used with ENABLE can be invoked. The /ELAN qualifier’s syntax is as follows:
DEFINE DEVICE/ELAN =(parent=parent device, name="ELAN NAME to join", size=1516 type=CSMACD Enable, Disable, description = "string")
|SET DEVICE/PVC||Sets the permanent virtual circuit (PVC) to be used by a Classical IP over ATM client. This is an optional qualifier. The list of PVCs is defined for use by CLIP clients. This command should be used before enabling the CLIP client. The PVC has to be set up manually in the ATM switch.||
LANCP> SET DEVICE/CONTENDER/MEDIA=UTP/NOEARLY/SOURCE ICA0
Enables monitor contention, UTP cable media, source routing and disables early token release for Token Ring device ICA0.
LANCP> SET DEVICE/MEDIA=TWI EWB0
Sets the media type to twisted pair for the second Tulip Ethernet device, EWB0.
LANCP> SET DEVICE EXA0/MOPDLL=ENABLE
Enables MOP downline load service for device EXA0, leaving the remaining MOPDLL parameters unchanged.
LANCP> SET DEVICE EXA0/MOPDLL=(ENABLE,EXCLUSIVE,SIZE=1482)
Enables MOP downline load service for device EXA0, in exclusive mode with the data transfer size of 1482 bytes, leaving the remaining MOPDLL parameters unchanged.
LANCP> SET DEVICE EXA0/MOPDLL=(ENABLE,NOEXCLUSIVE) LANCP> SET DEVICE FXA0/MOPDLL=(ENABLE,EXCL,KNOWN)
These commands enable LANACP MOP downline load service for: