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.
Note
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
On Alpha systems, same as the /PARAMETERS qualifier./COUNTERS
Displays device counters.Devices: All LAN devices; template devices only.
/DLL
On Alpha systems, same as the /MOPDLL qualifer. They show downline load characteristics.
/MAP
Displays the current configuration of the functional address mapping table.Devices: Token Ring devices; template devices only.
/MOPDLL
Displays LAN volatile device database information related to MOP downline load for the device./PARAMETERS
Displays status and related information about the device.Devices: All LAN devices
/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.Devices: LAN devices; template devices only.
/SR_ENTRY
Displays the contents of the current source routing cache table.Devices: Token Ring devices; template devices only.
Examples
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
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
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
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
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
LANCP> SHOW DEVICE/REVISION FXA0 Device revision FXA0: 05140823
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 is the same as the SHOW MOPDLL.
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.
None.
LANCP> SHOW LOG SYS$MANAGER:LAN$ACP.LOG latest contents: 17-MAR-1996 07:29:51.71 Volunteered to load request on EXA0 from HELENA Requested file: LAVC$SYSDEVICE:<SYS1A.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE 17-MAR-1996 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-1996 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-1996 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-1996 07:29:57.36 Volunteered to load request on EXA0 from HELENA Requested file: LAVC$SYSDEVICE:<SYS1A.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE 17-MAR-1996 07:29:58.49 Volunteered to load request on EXA0 from AJAX Requested file: LAVC$SYSDEVICE:<SYS10.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE 17-MAR-1996 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-1996 07:30:03.66 Volunteered to load request on EXA0 from AJAX Requested file: LAN$DLL:ONE.SYS 17-MAR-1996 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-1996 07:30:04.79 Volunteered to load request on EXA0 from AJAX Requested file: LAN$DLL:ONE.SYS 17-MAR-1996 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 the current state of MOP downline load services for the system, including devices for which MOP loading is enabled and counters information.
SHOW MOPDLL
None.
None.
LANCP>SHOW MOPDLL LAN MOP 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 23-SEP-1994 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 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=command-file-name
Creates the specified file and directs output there 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.
Examples
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-1996 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-1996 09:11:17.29
LANCP> SHOW NODE VAXSYS
LANCP> SHOW NODE/ALL VAX
LANCP> SHOW NODE/ALL
LANCP> SHOW NODE/ALL/OUTPUT=TMP.INI
Creates a subprocess of the current process. The SPAWN command copies the context of the subprocess from the current process.
SPAWN [command-string]
command-string
A string of commands to be executed in the context of the created subprocess. After the command string is executed, control returns to LANCP.
None.
LANCP> SPAWN $ MC LANCP LANCP> DEFINE NODE BOOM/ROOT=LAVC$SYSDEVICE:<SYS22.> LANCP> SPAWN SEARCH LAVC$SYSDEVICE:[*.SYSEXE]MOD*.DAT BOOM ****************************** LAVC$SYSDEVICE:[SYS1A.SYSEXE]MODPARAMS.DAT;1 SCSNODE="BOOM " LANCP> DEFINE NODE BOOM/ROOT=LAVC$SYSDEVICE:<SYS1A.>
In this example, you enter the node information for a node, but are unsure of the root, so you spawn to search MODPARAMS.DAT for the node name and then correct the root.
Issues a request to reboot to a remote node.Rather than specify the format to send MOP Version 3 or 4, the LANCP utility sends one message in each format to the target node.
TRIGGER NODE node-specification
node-specification
Supplies either the node name or the node address of the target node. If you supply the node name, the node address is obtained by looking up the node name in the LAN volatile node database. If you supply the node address, the corresponding node need not be defined in the LAN volatile node database. The canonical form of the address consists of 6 hexadecimal byte characters separated by hyphens. Use a colon as the separator character to indicate the bit-reversed form of the address.
/DEVICE=device-name
Specifies the LAN controller device name to be used for sending the trigger boot messages. For example, you can specify a DEMNA controller as EXA, EXA0 or EXA0:./PASSWORD=16hexdigits
Supplies the password to be used when the connection is initiated, in hexadecimal (for example, /PASSWORD=0123456789ABCDEF). The default password is zero. You can omit leading zeros.
Examples
LANCP> TRIGGER NODE GALAXY/DEVICE=EWA0)
LANCP> TRIGGER NODE 08-00-2B-11-22-33/DEVICE=EWA0/PASSWORD=0123456789AB
On Alpha systems, updates firmware image for a device. Requires SYSPRV privilege.
UPDATE DEVICE device-name
device-name
Specifies a device whose firmware is to be updated. 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.
/FILE = filename
Specifies the name of the file that is to be loaded into the EEPROM of the LAN device./RESET (default)
/NORESET
Specifies whether the device is to be reset after it has been updated. Normally, a reset is done to get the device to begin running the new firmware.
LANCP> UPDATE DEVICE FAA0/FILE=FBUS_MAIN.SYS
Updates FDDI device FAA0 with the firmware file FBUS_MAIN.SYS followed by a reset.
LATCP allows you to control the LAT software on a node and to obtain information from it. For example, you can use LATCP to create services on the local node, to associate a port on the local node with a service or device on a remote terminal server, and to display information about services offered on the local node or on other nodes in the network.
When you use LATCP commands to change LAT characteristics (such as creating a service and associating a port with a service), the changes take effect immediately. However, when the LAT port driver stops, these characteristics are lost. If you want these characteristics to be present the next time you start the LAT port driver, edit LAT$SYSTARTUP.COM by modifying or adding commands to set these characteristics. Then, invoke LAT$STARTUP.COM to start the LAT port driver. (See the OpenVMS System Manager's Manual for more information.)
RUN SYS$SYSTEM:LATCP
To invoke LATCP, enter RUN SYS$SYSTEM:LATCP at the DCL command prompt. At the LATCP> prompt, you can enter the LATCP commands described in the following section.To exit from LATCP, enter the EXIT command at the LATCP> prompt or press Ctrl/Z.
You can also execute a single LATCP command by using a DCL string assignment statement, as shown in the following example:
$ LCP :== $LATCP $ LCP SET NODE/STATE=ONLATCP executes the SET NODE command and returns control to DCL.
Command | Function |
---|---|
ATTACH | Transfers control from your current process to the specified process. |
CREATE LINK | Creates LAT data links. |
CREATE PORT | Creates a logical port on the local node. |
CREATE SERVICE | Creates a service on a service node. |
DEFINE/KEY | Assigns a command string to a function key on your keypad. |
DELETE LINK | Deletes a LAT data link from a node. |
DELETE PORT | Deletes an application port or dedicated port. |
DELETE QUEUE_ENTRY | Deletes an incoming queued request from the local node. |
DELETE SERVICE | Deletes a service on a service node. |
EXIT | Returns the user to DCL command level. |
HELP | Displays help text for LATCP commands. |
RECALL | Recalls LATCP commands that you entered previously so that you can execute them again. |
REFRESH | Refreshes your display screen, for example, after your display has been overwritten by output from some other source. |
SCROLL | Allows you to retrieve information that has scrolled off the screen. |
SET LINK | Modifies characteristics of LAT data links. |
SET NODE | Specifies LAT characteristics for a node. |
SET PORT | Maps a logical port on a node to either a remote device on a terminal server or a special application service on a remote LAT service node. |
SET SERVICE | Changes service characteristics. |
SHOW LINK | Displays the characteristics of links on your node. |
SHOW NODE | Displays the characteristics of nodes. |
SHOW PORT | Displays port characteristics. |
SHOW QUEUE_ENTRY | Displays information about requests, or entries, queued on the local node. |
SHOW SERVICE | Displays characteristics of LAT services known to your node. |
SPAWN | Creates a subprocess. |
ZERO COUNTERS | Resets the node counters, service counters, and link counters maintained by your node. |
6048P026.HTM OSSG Documentation 26-NOV-1996 12:42:57.27
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.