Previous | Contents | Index |
Note that specifying the file name explicitly in the boot command overrides the file name specified in the node database entry.
Displays the current settings for LANCP and LANACP.
SHOW ACP
None.
/OUTPUT=file-name
Creates the specified file and directs output to it.
LANCP> SHOW ACP LANCP/LANACP options: Verify is OFF OPCOM messages are ENABLED DLL packet tracing is DISABLED |
This example shows how LANCP and LANACP are currently configured.
Displays a list of LAN devices and characteristics on the system.
SHOW CONFIGURATION
None.
/OUTPUT=file-name
Creates the specified file and directs output to it./USERS
Shows which protocols are using which template device.
LANCP> SHOW CONFIGURATION/USERS LAN Configuration:
|
This example shows the output from a SHOW CONFIGURATION/USERS command entered on a node with 17 LAN devices, 4 of which are actively in use.
Displays information in the volatile device database. If the LANACP process is not running, displays a list of current LAN devices.
SHOW DEVICE device-name
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.
If you do not specify a qualifier, the utility displays the matching devices without additional information. |
/ALL
Shows all devices that match device name./CHARACTERISTICS or PARAMETERS
Displays status and related information about the device./COUNTERS
Displays device counters./DLL or MOPDLL
Displays LAN volatile device database information related to MOP downline load for the device./INTERNAL_COUNTERS
Displays internal counters. By default, it does not display zero counters. To see all counters, including zero, use the additional qualifier /ZERO. To see the debug counters, use the additional qualifier /DEBUG./MAP
Displays the current configuration of the functional address mapping table./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./OUTPUT=file-name
Creates the specified file and directs output to it./REVISION
Displays the current LAN driver and device revision information, if available or applicable. Not all LAN drivers maintain revision information./SR_ENTRY
Displays the contents of the current Token Ring source routing cache table./TRACE
Displays LAN driver trace data./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 (GARP (Generic Attribute Registration Protocol) VLAN Registration Protocol) packets that contain the configuration information and displays the configured tags.The switch periodically sends GVRP 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 driver has configured.
#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 EWF0 Device Revisions EWF0: Value Component ----- --------- 02000041 Device hardware revision 08020110 00000004 Port driver revision 08020172 00000001 LAN common routines revision |
This command displays revision information for Ethernet device EWF0:.
#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.
Displays the current state of MOP downline load services for the system, including devices for which MOP loading is enabled and counters information.
SHOW DLL or MOPDLL
None.
/OUTPUT=file-name
Creates the specified file and directs output to it.
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-2002 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.
Displays recent downline load activity (the last 2048 bytes of log data written to the log file SYS$MANAGER:LAN$ACP.LOG).
SHOW LOG
None.
/OUTPUT=file-name
Creates the specified file and directs output to it.
LANCP> SHOW LOG SYS$MANAGER:LAN$ACP.LOG latest contents: 17-MAR-2005 07:29:51.71 Volunteered to load request on EXA0 from HELENA Requested file: LAVC$SYSDEVICE:<SYS1A.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE 17-MAR-2005 07:29:53.00 Load succeeded for HELENA on EXA0 MOP V3 format, System image, LAVC$SYSDEVICE:<SYS1A.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE Packets: 84 sent, 84 received Bytes: 121492 sent, 168 received, 120988 loaded Elapsed time: 00:00:01.09, 110998 bytes/second 17-MAR-2005 07:29:53.60 Could not respond to load request on EXA0 from AJAX, file not found Requested file: LAN$DLL:READ_ADDR.SYS 17-MAR-2005 07:29:54.46 Could not respond to load request on EXA0 from AJAX, file not found Requested file: LAN$DLL:READ_ADDR.SYS 17-MAR-2005 07:29:57.36 Volunteered to load request on EXA0 from HELENA Requested file: LAVC$SYSDEVICE:<SYS1A.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE 17-MAR-2005 07:29:58.49 Volunteered to load request on EXA0 from AJAX Requested file: LAVC$SYSDEVICE:<SYS10.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE 17-MAR-2005 07:29:59.49 Load succeeded for HELENA on EXA0 MOP V3 format, System image, LAVC$SYSDEVICE:<SYS1A.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE Packets: 84 sent, 84 received Bytes: 121492 sent, 168 received, 120988 loaded Elapsed time: 00:00:01.73, 69935 bytes/second 17-MAR-2005 07:30:03.66 Volunteered to load request on EXA0 from AJAX Requested file: LAN$DLL:ONE.SYS 17-MAR-2005 07:30:04.05 Load succeeded for AJAX on EXA0 MOP V3 format, System image, LAN$DLL:ONE.SYS Packets: 9 sent, 9 received Bytes: 11354 sent, 18 received, 11300 loaded Elapsed time: 00:00:00.04, 282500 bytes/second 17-MAR-2005 Requested file: LAN$DLL:ONE.SYS 17-MAR-2005 07:30:05.18 Load succeeded for AJAX on EXA0 MOP V3 format, System image, LAN$DLL:ONE.SYS Packets: 9 sent, 9 received Bytes: 11354 sent, 18 received, 11300 loaded Elapsed time: 00:00:00.04, 282500 bytes/second |
This command displays the last 2048 bytes of log data written to the log file SYS$MANAGER:LAN$ACP.LOG.
Displays information in the LAN volatile node database.
SHOW NODE node-name
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.
/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./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./TOTAL
Display counter totals only, for the nodes selected.
#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 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 12-JUN-2002 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 12-JUN-2002 09:11:17.29 |
This example shows output from a command issued on a local node on which there are three nodes defined (GALAXY and CALPAL). CALPAL has issued two load requests:
- The first request is the multicast request from CALPAL that the local node volunteered to accept.
- 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.
Previous | Next | Contents | Index |