1 – DEVICE
Displays information in the LAN permanent device database.
Format
LIST DEVICE device-name
1.1 – Parameter
device-name
Specifies the LAN device name. The device name has the form ddcu, where
dd is the device identifier, 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 EI Ethernet device is specified as EIA0,
the second as EIB0, and so on. You can specify the first EI device, for
example, as EIA, EIA0, or EIA0:.
A partial device name selects all matching devices. For example: E to
select all Ethernet devices, V for VLAN devices, EI for Ethernet EI
devices, no device name to select all LAN devices.
1.2 – Qualifiers
1.2.1 /ALL
Lists all matching LAN devices in the LAN permanent device database.
If no device name is provided, all devices are listed.
LIST and SHOW commands implicitly include this qualifier.
1.2.2 /BANDWIDTH
Lists BANDWIDTH settings for devices.
1.2.3 /CHARACTERISTICS
/CHARACTERISTICS or /PARAMETERS
Lists device characteristics.
1.2.4 /DLL
/DLL or /MOPDLL
Displays MOP downline load settings.
1.2.5 /OUTPUTFILE
/OUTPUTFILE=filespec
Writes command output to the specified file.
1.2.6 /PTP
(Future release, not currently supported)
Lists PTP settings for devices.
1.2.7 /TEST
Lists test characteristics set for each device.
1.2.8 /TRACE
Lists driver trace parameters set for each device.
1.2.9 /ULAN
/ULAN or /UDP
(Future Release, not currently supported)
Lists UDP LAN devices and characteristics.
1.2.10 /VLAN
Lists VLAN devices and characteristics.
1.3 – Examples
1 LANCP> LIST DEVICE/DLL
Device Listing, permanent database:
--- MOP Downline Load Service Characteristics ---
Device State Access Mode Clients Data Size
------ ----- ----------- ------- ---------
EIA0 Enabled Exclusive KnownClientsOnly 1400 bytes
EWA0 Disabled NoExclusive NoKnownClientsOnly 246 bytes
This command displays MOP downline load information in the LAN
permanent device database for all known devices.
2 – NODE
Displays information in the LAN permanent node database, especially MOP
downline load information.
Format
LIST NODE node-name
2.1 – Parameter
node-name
Specifies the name of a node in the LAN permanent node database.
A partial node name selects all matching nodes. For example: A to
select all nodes starting with A, no node name to select all nodes.
2.2 – Qualifiers
2.2.1 /ALL
Lists all matching nodes in the LAN permanent node database.
If no node name is provided, all nodes are listed.
LIST and SHOW commands implicitly include this qualifier.
2.2.2 /COMFILE
/COMFILE=filespec
Writes command output to the specified file in the form of a list
of DEFINE NODE commands. The resulting command file can be used to
populate the LAN node database.
2.2.3 /OUTPUTFILE
/OUTPUTFILE=filespec
Writes command output to the specified file.
2.3 – Example
LANCP> LIST 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-2018 09:11:17
on EIA0 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-2018 09:11:17.29
This example shows output from a LIST NODE command issued on a system
with three nodes defined (GALAXY, ZAPNOT, and CALPAL). CALPAL has issued
two load requests:
o The first request is the multicast request from CALPAL that this
system volunteered to accept.
o The second request is the load request sent directly to this system
by CALPAL for the actual load data. The elapsed time from the second
load request to completion of the load was 6.65 seconds.