VMS Help LANCP, SHOW *Conan The Librarian (sorry for the slow response - running on an old VAX) |
1 - CONFIGURATION |
Displays a list of LAN devices and characteristics on the system. Format SHOW CONFIGURATION
1.1 - Parameters
None.
1.2 - Qualifiers
1. 2.1 - /OUTPUT
/OUTPUT=file-name Creates the specified file and directs output to it.
1. 2.2 - /USERS
On Alpha systems, shows which protocols are using which template device.
1.3 - Example
LANCP> SHOW CONFIGURATION LAN Configuration: Device Medium Default LAN Address Version ------ ------ ------------------- ------- EWA0 CSMA/CD 08-00-2B-E4-00-BF 02000023 EWB0 CSMA/CD 08-00-2B-92-A4-0D 02000023 IRA0 Token Ring 00-00-93-58-5D-32 20000223 This example shows the output from a SHOW CONFIGURATION command that was entered on a node that has three LAN devices, two DE435s, and a DETRA. The version is the device-specific representation of the actual (hardware or firmware) version. In this example, for two devices on the PCI bus, the actual version is in the low byte (2.3 for the DE435 adapters). A device that does not have a readable version is shown as version zero. Consult your device-specific documentation to correlate the version returned with a particular hardware or firmware implementation of the device.
2 - DEVICE |
Displays information in the volatile device database. If the LANACP process is not running, displays a list of current LAN devices. Format SHOW DEVICE device-name
2.1 - Parameter
device-name Supplies the LAN controller device name. The device name has the form ddcu where dd is the device code, c is the controller designation, and u is the unit number. LAN devices are specified as the name of the template device which is unit 0. For example, the first DE435 Ethernet device is specified as EWA0, the second as EWB0. For example, you can specify a DEMNA controller as EXA, EXA0, or EXA0:. This refers to the LAN template device, for which is maintained most of the device parameters and counters. Also, the device name can refer to a device unit representing an actual user or protocol. For example, the cluster protocol can be started on a device as EWA1. You can specify specific device units to view unit-specific parameter information. If you do not specify a device name, all devices are displayed. If you specify a device name, all matching LAN devices are displayed, for example: E to select all Ethernet devices, F for FDDI, I for Token Ring, EW to select all Ethernet PCI Tulip devices. NOTE If you do not specify a qualifier, the utility displays the matching devices without additional information.
2.2 - Qualifiers
2. 2.1 - /ALL
Shows all devices that match device name.
2. 2.2 - /CHARACTERISTICS
On Alpha systems, same as the /PARAMETERS qualifier.
2. 2.3 - /COUNTERS
Displays device counters.
2. 2.4 - /DLL
Displays LAN volatile device database information related to MOP downline load for the device.
2. 2.5 - /MAP
Displays the current configuration of the functional address mapping table.
2. 2.6 - /MOPDLL
Same as the /DLL qualifier.
2. 2.7 - /OUTPUT
/OUTPUT=file-name Creates the specified file and directs output to it.
2. 2.8 - /PARAMETERS
Displays status and related information about the device.
2. 2.9 - /REVISION
Displays the current firmware revision of the device, if available or applicable. Not all LAN devices return revision information. LAN devices that do not have a revision display a revision of zero.
2. 2.10 - /SR_ENTRY
Displays the contents of the current Token Ring source routing cache table.
2.3 - Examples
1.LANCP> SHOW DEVICE/COUNTERS EXA0 Device Counters EXA0: Value Counter ----- ------- 259225 Seconds since last zeroed 5890496 Data blocks received 4801439 Multicast blocks received 131074 Receive failure 764348985 Bytes received 543019961 Multicast bytes received 3 Data overrun 1533610 Data blocks sent 115568 Multicast packets transmitted 122578 Blocks sent, multiple collisions 86000 Blocks sent, single collision 189039 Blocks sent, initially deferred 198120720 Bytes sent 13232578 Multicast bytes transmitted 7274529 Send failure 0 Collision detect check failure 0 Unrecognized frame destination 0 System buffer unavailable 0 User buffer unavailable This command displays counters for Ethernet device EXA0. 2.LANCP> SHOW DEVICE/MAP ICA0 Multicast to Functional Address Mapping ICA0: Multicast address Functional Address Bit-Reversed ----------------- ------------------ ------------ 09-00-2B-00-00-04 03-00-00-00-02-00 C0:00:00:00:40:00 09-00-2B-00-00-05 03-00-00-00-01-00 C0:00:00:00:80:00 CF-00-00-00-00-00 03-00-00-08-00-00 C0:00:00:10:00:00 AB-00-00-01-00-00 03-00-02-00-00-00 C0:00:40:00:00:00 AB-00-00-02-00-00 03-00-04-00-00-00 C0:00:20:00:00:00 AB-00-00-03-00-00 03-00-08-00-00-00 C0:00:10:00:00:00 09-00-2B-02-00-00 03-00-08-00-00-00 C0:00:10:00:00:00 09-00-2B-02-01-0A 03-00-08-00-00-00 C0:00:10:00:00:00 AB-00-00-04-00-00 03-00-10-00-00-00 C0:00:08:00:00:00 09-00-2B-02-01-0B 03-00-10-00-00-00 C0:00:08:00:00:00 09-00-2B-00-00-07 03-00-20-00-00-00 C0:00:04:00:00:00 09-00-2B-00-00-0F 03-00-40-00-00-00 C0:00:02:00:00:00 09-00-2B-02-01-04 03-00-80-00-00-00 C0:00:01:00:00:00 09-00-2B-02-01-07 03-00-00-02-00-00 C0:00:00:40:00:00 09-00-2B-04-00-00 03-00-00-04-00-00 C0:00:00:20:00:00 09-00-2B-02-01-00 03-00-00-00-08-00 C0:00:00:00:10:00 09-00-2B-02-01-01 03-00-00-00-10-00 C0:00:00:00:08:00 09-00-2B-02-01-02 03-00-00-00-20-00 C0:00:00:00:04:00 03-00-00-00-00-01 03-00-00-00-00-01 C0:00:00:00:00:80 03-00-02-00-00-00 03-00-02-00-00-00 C0:00:40:00:00:00 This command displays mapping information for Token Ring device ICA0. 3.LANCP> SHOW DEVICE/MOPDLL Device Listing, volatile database: --- MOP Downline Load Service Characteristics --- Device State Access Mode Clients Data Size ------ ----- ----------- ------- --------- EXA0 Enabled Exclusive KnownClientsOnly 1400 bytes FXA0 Disabled NoExclusive NoKnownClientsOnly 246 bytes This command displays MOP downline load information in the LAN volatile device database for all known devices. 4.LANCP> SHOW DEVICE/MOPDLL EXA0 Device Listing, volatile database: --- MOP Downline Load Service Characteristics --- Device State Access Mode Clients Data Size ------ ----- ----------- ------- --------- EXA0 Enabled Exclusive KnownClientsOnly 1400 bytes This command displays MOP downline load information in the LAN volatile device database for device EXA0. 5.LANCP> SHOW DEVICE/PARAMETERS IRA0 Device Parameters IRA0: Value Parameter ----- --------- Normal Controller mode External Internal loopback mode 00-00-93-58-5D-32 Hardware LAN address Token Ring Communication medium Enabled Functional address mode No Full duplex enable No Full duplex operational 16 Line speed (megabits/second) 16 Mbps Ring speed STP Line media Enabled Early token release Disabled Monitor contender 200 SR cache entries 2 SR discovery timer 60 SR Aging Timer Enabled Source routing 3 Authorized access priority AA-00-04-00-92-FF Upstream neighbor 0 Ring number This command displays status and parameters information for Token ring device IRA0. 6.LANCP> SHOW DEVICE/REVISION FXA0 Device revision FXA0: 05140823 This command displays revision information for FDDI device FXA0. 7.LANCP> SHOW DEVICE/SR_ENTRY ICA0 Source Routing Cache Table ICA0: LAN address State XmtTmo RcvTmo StaleTmo DiscvTmo ----------------- ----- -------- -------- -------- -------- AA-00-04-00-92-FF LOCAL 00000028 00000028 00000245 00000000 This command displays source routing entry information for Token Ring device ICA0.
3 - DLL |
Displays the current state of MOP downline load services for the system, including devices for which MOP loading is enabled and counters information. Format SHOW DLL
3.1 - Parameters
None.
3.2 - Qualifier
3. 2.1 - /OUTPUT
/OUTPUT=file-name Creates the specified file and directs output to it.
3.3 - Example
LANCP>SHOW DLL LAN DLL Status: EXA enabled in exclusive mode for known nodes only, data size 1482 bytes FXA disabled #Loads Packets Bytes Last load time Last loaded ------ ------- ----- -------------------- ------------ EXA 5 1675 4400620 22-SEP-2000 10:27.51 GALAXY FXA 0 0 0 On this node, there are two LAN devices, EXA (DEMNA) and FXA (DEMFA). MOP downline load service is enabled on EXA in exclusive mode. Requests are answered only for nodes that are defined in the LANACP node database. The image data size in the load messages is 1482 bytes. There have been five downline loads, the last one occurring on node GALAXY at 10:27. Finally, there are no recorded downline loads for FXA, which is currently disabled for downline load service.
4 - LOG |
Displays recent downline load activity (the last 2048 bytes of log data written to the log file SYS$MANAGER:LAN$ACP.LOG). Format SHOW LOG
4.1 - Parameters
None.
4.2 - Qualifier
4. 2.1 - /OUTPUT
/OUTPUT=file-name Creates the specified file and directs output to it.
4.3 - Example
LANCP> SHOW LOG This command displays the last 2048 bytes of log data written to the log file SYS$MANAGER:LAN$ACP.LOG.
5 - NODE |
Displays information in the LAN volatile node database. Format SHOW NODE node-name
5.1 - Parameter
node-name Specifies the name of a node in the LAN volatile node database. The name can include up to 63 characters associated with the node address. If you do not specify a node name, all nodes are displayed.
5.2 - Qualifiers
5. 2.1 - /ALL
Displays information for all nodes in the LAN volatile node database. If you specify a node name, all matching nodes are selected; for example, A/ALL selects all nodes beginning with A.
5. 2.2 - /OUTPUT
/OUTPUT=file-name Creates the specified file and directs output to that file. If the file extension is .com, the output is in the form of a list of DEFINE NODE or SET NODE commands. The resulting command file can be used to create the LAN node databases.
5. 2.3 - /TOTAL
Display counter totals only, for the nodes selected.
5.3 - Examples
1.LANCP> SHOW NODE Node Listing: GALAXY (08-00-2B-2C-51-28): MOP DLL: Load file: APB.EXE Load root: $64$DIA24:<SYS11.> Boot type: Alpha satellite ZAPNOT (08-00-2B-18-7E-33): MOP DLL: Load file: NISCS_LOAD.EXE Load root: LAVC$SYSDEVICE:<SYS10.> Boot type: VAX satellite CALPAL (08-00-2B-08-9F-4C): MOP DLL: Load file: READ_ADDR.SYS Last file: LAN$DLL:APB_X5WN.SYS Boot type: Other 2 loads requested, 1 volunteered 1 succeeded, 0 failed Last request was for a system image, in MOP V4 format Last load initiated 10-JUN-1998 09:11:17 on EXA0 for 00:00:06.65 527665 bytes, 4161 packets, 0 transmit failures Unnamed (00-00-00-00-00-00): Totals: Requests received 2 Requests volunteered 1 Successful loads 1 Failed loads 0 Packets sent 2080 Packets received 2081 Bytes sent 523481 Bytes received 4184 Last load CALPAL at 10-JUN-1998 09:11:17.29 This example shows output from a command issued on a local node on which there are three nodes defined (GALAXY, ZAPNOT, and CALPAL). CALPAL has issued two load requests: o The first request is the multicast request from CALPAL that the local node volunteered to accept. o The second request is the load request sent directly to the local node by CALPAL for the actual load data. The elapsed time from the second load request to completion of the load was 6.65 seconds. 2.LANCP> SHOW NODE VAXSYS Displays node characteristics and counters information from the LAN volatile node database for node VAXSYS. 3.LANCP> SHOW NODE/ALL VAX Displays node characteristics and counters information from the LAN volatile node database for all nodes whose name begins with VAX. 4.LANCP> SHOW NODE/ALL Displays node characteristics and counters information from the LAN volatile node database for all nodes. 5.LANCP> SHOW NODE/ALL/OUTPUT=TMP.INI Writes a list of all nodes to the file TMP.INI.
|