1  LIST
 

2  DEVICE
   Displays information in the LAN permanent device database.

   Format

     LIST DEVICE  device-name
 

3  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 a device unit 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.
 

3  Qualifiers
 

/ALL

   Lists all devices in the LAN permanent device database.
 

/CHARACTERISTICS

      /CHARACTERISTICS or /PARAMETERS

   Lists status and related information about the device.
 

/DLL

      /DLL or /MOPDLL

   Displays MOP downline load characteristics.
 

/MAP

   Lists the current configuration of the functional address mapping
   table for a Token Ring device.
 

/OUTPUT

      /OUTPUT=file name

   Creates the specified file and directs output to it.
 

/SR_ENTRY

   Lists the contents of the current source routing cache table.
 

/TRACE

   Lists driver trace parameters set for the device.
 

3  Examples

   1.LANCP> LIST DEVICE/MOPDLL

     Device Listing, permanent  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
     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
 

3  Parameter
 

node-name

   Specifies the node name. The name can include up to 63 characters
   associated with the node address. If no node name is given, all
   nodes are displayed.
 

3  Qualifiers
 

/ALL

   Displays data for all nodes in the LAN permanent node database.
   If you specify a node name, all matching nodes are selected; for
   example, A/ALL selects all nodes beginning with A.
 

/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.
 

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 30-OCT-1994 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 LIST NODE 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.