Document revision date: 30 March 2001

## OpenVMS System Management Utilities Reference Manual

Previous | Contents | Index

This command sets up node CALPAL for booting an InfoServer image. It defines the file that should be loaded when a load request without a file name is received from node CALPAL.

Because the file does not include a directory specification, the logical name LAN$DLL defines where to locate the file. You could give directory specification using the file name or by using the /ROOT qualifier.

Note that specifying the file name explicitly in the boot command overrides the file name specified in the node database entry.

## EXIT

> Stops execution of LANCP and returns control to the DCL command level. You can also enter Ctrl/Z at any time to exit.

### Format

> EXIT

### Parameters

> None.

### Qualifiers

> None.

### Example

    LANCP> EXIT
    $

> This command stops execution of LANCP and returns control to the DCL command level.

## HELP

> Provides online help information about the LANCP utility.

### Format

> HELP [topic]

### Parameter

> #### topic

> Specifies a subject for which you want information---a LANCP command or LANCP command and command keyword. If you enter the HELP command with a command name only, such as HELP SET, LANCP displays a list of all of the command keywords used with the SET command.

### Qualifiers

> None.

### Example

    LANCP> HELP DEFINE DEVICE
    DEFINE

      DEVICE

            DEVICE device-name/qualifiers
            DEVICE/ALL/qualifiers

          Sets device specific parameters for the specified LAN devices.

          Requires SYSPRV privilege.

        Additional information available:

        Parameters Qualifiers
        /ALL  /ATMADDRESS /DLL /ELAN /MOPDLL    /VOLATILE_DATABASE    /UPDATE
        Examples

    DEFINE DEVICE Subtopic?

> This command provides online help for the LANCP command DEFINE DEVICE.

## LIST DEVICE

> Displays information in the LAN permanent device database.

### Format

> LIST DEVICE device-name

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

### Qualifiers

> #### /ALL

> Lists all devices in the LAN permanent device database.

> #### /CHARACTERISTICS

> On Alpha systems, lists status and related information about the device. It is the same as /PARAMETERS qualifier.

> #### /DLL

> Displays MOP downline load characteristics.

> #### /MAP

> Lists the current configuration of the functional address mapping table.

> #### /MOPDLL

> Same as /DLL qualifier.

> #### /OUTPUT=file name

> Creates the specified file and directs output to it.

> #### /PARAMETERS

> On Alpha systems, lists status and related information about the device.

> #### /SR_ENTRY

> On Alpha systems, lists the contents of the current source routing cache table.

###

#### 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
    LANCP> LIST DEVICE/MOPDLL EXA0

    Device Listing, permanent 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 permanent device database for device EXA0.

## LIST NODE

> Displays information in the LAN permanent node database, especially MOP downline load information.

### Format

> LIST NODE node-name

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

### 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=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.

### 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-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 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:

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

## PURGE DEVICE

> Deletes a device from the LAN permanent device database. Requires SYSPRV privilege.

### Format

> PURGE DEVICE device-name

### 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:. To select all LAN devices, omit the device name and include the /ALL qualifier.

### Qualifier

> #### /ALL

> Deletes all LAN devices in the LAN permanent device database. If you specify a device name, all matching LAN devices are selected, for example: E to select all Ethernet devices, F for FDDI, I for Token Ring, EW to select all Ethernet PCI Tulip devices.

### Example

    LANCP> PURGE DEVICE/ALL

> This command deletes all devices from the LAN permanent device database.

## PURGE NODE

> Deletes a node from the LAN permanent node database. Requires SYSPRV privilege.

### Format

> PURGE NODE node-name

### Parameter

> #### node-name

> Supplies the name of a node in the LAN permanent node database.

### Qualifier

> #### /ALL

> Deletes all LAN nodes in the LAN permanent node database. If you specify a node name, all matching nodes are selected; for example, A/ALL deletes all nodes whose name begins with A.

### Example

    LANCP> PURGE NODE/ALL

> This command deletes all nodes from the LAN permanent node database.

## SET ACP

> Modifies the operation of the LANACP LAN Server process. Requires SYSPRV privilege.

### Format

> SET ACP

### Parameters

> None.

### Qualifiers

> #### /ECHO

> #### /NOECHO (default)

> Enables partial tracing of received and transmitted downline load messages (the first 32 bytes of the data portion of each message). Note that the last one or two MOP messages are displayed in full: the memory load message with cluster parameters, and the parameter load with transfer address message, where present in the load.

> The data is written to a log file SYS$MANAGER:LAN$node-name.LOG.

> To obtain the entire contents of each message, use the /FULL qualifier as follows:

> `SET ACP/ECHO/FULL`

> #### /FULL

> #### /NOFULL (default)

> When /ECHO is enabled, displays the entire contents of received and transmitted downline load messages.

> #### /OPCOM (default)

> #### /NOOPCOM

> Enables OPCOM messages from LANACP LAN Server process.

> Messages are generated by the LANACP LAN Server process when a device status changes, load requests are received, and loads complete. These messages are displayed on the operator's console and included in the log file written by LANACP, SYS$MANAGER:LAN$ACP.LOG.

> #### /STOP

> Stops the LANACP process. It can be restarted by reexecuting the SYS$STARTUP:LAN$STARTUP command file.

### Example

    LANCP> SET ACP/ECHO/FULL

> This command enables tracing of received and transmitted downline load messages. The /FULL qualifier displays the entire contents of received and transmitted downline load messages.

## SET DEVICE (Alpha only)

> On Alpha systems, sets or modifies LAN device parameters. Requires PHY_IO privilege.

### Format

> SET DEVICE device-name

### Parameter

> #### device-name

> Specifies a device to be entered in the LAN volatile device database, or whose parameters are to be modified. 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.

### Qualifiers

> #### /AGING_TIMER=value

> Sets the amount of time in seconds to age Token Ring source routing cache entries before marking them stale. This timer expires when no traffic is sent to or received from the remote node in this amount of time. The default value is 60 seconds.

> Increase this value when idle connections bounce between the stale and known states. Setting this value too low may cause unnecessary explorer traffic to traverse the LAN.

> #### /ALL

> Sets data for all LAN devices. If you specify a device name, all matching LAN devices are selected, for example: E to select all Ethernet devices, F for FDDI, I for Token Ring, EW to select all Ethernet PCI Tulip devices.

> #### /ATMADDRESS=LES

> Sets the LAN emulation server (LES) address for asynchronous transfer mode (ATM). Usually the address is not user specified, and this qualifier is used only if you want a specific address. By default the address is determined by software from the configuration server for the LES.

> The /ATMADDRESS=LES qualifier's syntax is as follows:

>     SET DEVICE/ATMADDRESS = ([NO]LES=the ATM server)

> #### /ATMADDRESS=ARP

> Sets the address resolution protocol (ARP) server address for Classical IP over ATM. This qualifier is required before a LIS is enabled if the local host is not the ARP server.

> The /ATMADDRESS=ARP qualifier's syntax is as follows:

>     SET DEVICE/ATMADDRESS = (ARP=atm_arp_server)

> #### /CACHE_ENTRIES=value

> Sets the number of entries to reserve for caching Token Ring source routing address entries. The default value is 200 entries.

> If your system directly communicates to a large number of systems, you may want to increase this number.

> #### /CLIP

> Sets the Classical Internet Protocol (CLIP) over ATM (RFC1577). The CLIP qualifier implements a data-link level device as a client and/or a server in a logical IP subnet (LIS). This allows the IP protocol to transmit Ethernet frames over the ATM network. The /CLIP = ENABLE command causes the system to join the LIS. The /CLIP = DISABLE command causes the client to leave the logical IP subnet.

> Note that a LIS requires a server, and there must be only one server for each subnet. Communication between subnets can only be performed by a router. There can only be one client for each ATM adapter.

> The /CLIP qualifier's syntax with standard Internet dotted notation is as follows:

>     SET DEVICE/CLIP =(ip_subnet=a.b.c.d,
>                       ip_address=a.b.c.d,
>                       parent=devnam,
>                       name="ip subnet name",
>                       enable, disable
>                       type = client|server)

> The meanings for the syntax for /CLIP are as follows:

> Option | Meaning
> --- | ---
> ip_address | Specifies the IP address of the CLIP client.
> ip_subnet | Specifies the subnet mask of the CLIP client.
> parent=devnam | Specifies the parent device name.
> name | Specifies a name for the LIS to aid in operations and diagnostics.
> type=client | Starts up a classical IP client only. This is the default.
> type=server | Starts up a classical IP server. Only one server for each LIS is allowed, and the server needs to be started first.
> type=(server,client) | Starts up a classical IP server and client.

> Keywords and their meaning for /CLIP are as follows:

> Keyword | Meaning
> --- | ---
> Enable | Joins the logical IP subnet.
> Disable | Causes a client to leave the logical IP subnet.

> #### /CONTENDER

> #### /NOCONTENDER (default)

> Specifies that the Token Ring device is to participate in the Monitor Contention process when it joins the ring. The /NOCONTENDER qualifier, directs the device not to challenge the current ring server.

> #### /DISCOVERY_TIMER=value

> Sets the number of seconds to wait for a reply from a remote node when performing the source Token Ring routing route discovery process. The default value is 2 seconds.

> If you have nodes that respond slowly on your extended LAN, you may need to increase this number to reduce the amount of explorer traffic that traverses your LAN.

> #### /DLL=(enable-option, exclusive-option, size-option, knownclientsonly-option)

> Provides the MOP downline load service settings for the device.

> Note that defaults apply to creation of an entry in the device database. If an existing entry is being modified, fields not specified remain unchanged.

> You can specify the following keywords with this qualifier:

> - enable-option
>     ENABLE
>     DISABLE (default)
>   Specify ENABLE or DISABLE to indicate that MOP downline load service should be enabled or disabled for the device.
> - exclusive-option
>     EXCLUSIVE
>     NOEXCLUSIVE (default)
>   Specify EXCLUSIVE to indicate that no other provider of MOP downline load service is allowed on the specified LAN device at the same time as LANACP. Specify NOEXCLUSIVE to indicate that the LAN MOP downline load service can coexist with other implementations (in particular, the DECnet Phase IV implementation that operates the MOP protocol in shared mode).
> - size-option
>     SIZE=value
>   Use SIZE=value to specify the size in bytes of the file data portion of each downline load message. The permitted range is 246 to 1482 bytes. The default value is 246 bytes, which should allow any client to load properly. Note that some clients may not support the larger size.
>   The recommended size for better load performance and less server overhead is the largest size that results in successful loads of all clients. The 1482 value is derived from the maximum packet size for CSMA/CD (Ethernet) of 1518 bytes less the 802e header and CRC (26 bytes) and MOP protocol overhead (10 bytes).
>   You can override the size on a per-node basis. See the DEFINE NODE and SET NODE commands for details.
> - knownclientsonly-option
>     KNOWNCLIENTSONLY
>     NOKNOWNCLIENTSONLY (default)
>   Specify KNOWNCLIENTSONLY to indicate that MOP downline load requests should be serviced only for clients defined in the LAN permanent node database. When NOKNOWNCLIENTSONLY is selected, LANACP searches the LAN$DLL directory for any images requested by clients that are not defined in the LAN permanent node database.

> #### /EARLY (default)

> #### /NOEARLY

> Enables Early Token Release on the device. The /NOEARLY qualifier, disables Early Token Release.

> #### /ELAN

> The /ELAN qualifier has two values: enable and disable. With /ELAN=ENABLE along with the keyword STARTUP, the LAN emulation is loaded when LANACP starts. With /ELAN=DISABLE, the same parameters used with ENABLE can be invoked.

> The /ELAN qualifier's syntax is as follows:

>     DEFINE DEVICE/ELAN =(parent=parent device,
>                          name="ELAN NAME to join",
>                          size=1516
>                          type=CSMACD
>                          Enable,
>                          Disable,
>                          description = "description string,")

> The meaning of the syntax for /ELAN is as follows:

> Option | Meaning
> --- | ---
> parent | The ATM adapter device name. An example of the parent device for DAPCA is: HW n0, where n is the controller number. An example of the parent device for DGLTA is: HC n0, where n is the controller number.
> name | Optionally specified if you want to join a specific ELAN. The default is null.
> size | Maximum frame size of the LAN you want to join. Valid sizes are 1516, 4544, or 9234 bytes. The default is 1516.
> type | Support currently only for CSMACD, which is the default.
> description | A method of describing the ELAN for display purposes only.

> Keywords and their meanings for /ELAN are as follows:

> Keyword | Meaning
> --- | ---
> Enable | Begins a join on a specified emulated LAN. It also loads the driver, if not already loaded.
> Disable | Causes a client to leave the emulated LAN.

> #### /FULL_DUPLEX

> #### /NOFULL_DUPLEX (default)

> Enables full-duplex operation of a LAN device. Before full-duplex operation results from the use of this qualifier, additional device or network hardware setup may be required. Some devices may be enabled for full-duplex operation by default. Some devices may not allow the setting to be changed.

> The /NOFULL_DUPLEX qualifier, disables full-duplex operation.

> #### /MAP=(MULTICAST_ADDRESS=address, FUNCTIONAL_ADDRESS=address)

> #### /NOMAP=(MULTICAST_ADDRESS=address)

> Maps a standard multicast address to a functional address. Token ring devices do not support IEEE 802 standard globally defined group addresses. They do support functional addresses. A functional address is a locally administered group address that has 31 possible values. Each functional address sets one bit in the third through sixth byte of the address and bytes 1 and 2 are 03-00 (C0:00 in bit reversed format).

> The /NOMAP=(MULTICAST_ADDRESS=address) qualifier, clears the mapping established for the specified address.

> Specify the functional address as follows:

> - The MULTICAST_ADDRESS argument requires a standard 6-byte multicast address.
> - The FUNCTIONAL_ADDRESS argument requires only the last 4 bytes of the functional address (the preceding 03-00 bytes are automatically prefixed).
> - The address variable, given as hexadecimal byte characters separated by hyphens, specifies the canonical form of the address. Use a colon as the separator character to indicate the bit-reversed form of the address.

> For example, to map the multicast address CB-00-01-02-03-04 to the functional address 03-00-00-80-00-00 on the Token Ring device IRA0, enter the following command:

>     SET DEVICE IRA0/MAP=(MULTI=CB-00-01-02-03-04,FUNCT=00:01:00:00)

> For the default address mapping, see Table 12-1 or issue the command SHOW DEVICE/MAP device-name.

> Table 12-1 Default Functional Address Mapping for Token Ring Devices
> Multicast Address | Functional Address | Description
> --- | --- | ---
> 09-00-2B-00-00-04 | 03-00-00-00-02-00 | ISO ALL ES
> 09-00-2B-00-00-05 | 03-00-00-00-01-00 | ISO ALL IS
> CF-00-00-00-00-00 | 03-00-00-08-00-00 | Loopback Assistant
> AB-00-00-01-00-00 | 03-00-02-00-00-00 | DNA MOP Dump/Load
> AB-00-00-02-00-00 | 03-00-04-00-00-00 | DNA MOP Remote Console
> AB-00-00-03-00-00 | 03-00-08-00-00-00 | DNA L1 Routers
> 09-00-2B-02-00-00 | 03-00-08-00-00-00 | DNA L2 Routers
> 09-00-2B-02-01-0A | 03-00-08-00-00-00 | DNA Phase IV Primary Router
> AB-00-00-04-00-00 | 03-00-10-00-00-00 | DNA Endnodes
> 09-00-2B-02-01-0B | 03-00-10-00-00-00 | DNA Phase IV Prime Unknown Destination
> 09-00-2B-00-00-07 | 03-00-20-00-00-00 | PCSA NETBIOS Emulation
> 09-00-2B-00-00-0F | 03-00-40-00-00-00 | LAT Service Advertisement
> 09-00-2B-02-01-04 | 03-00-80-00-00-00 | LAT Service Solicit
> 09-00-2B-02-01-07 | 03-00-00-02-00-00 | LAT Xwindown Service Solicit
> 09-00-2B-04-00-00 | 03-00-00-04-00-00 | LAST
> 09-00-2B-02-01-00 | 03-00-00-00-08-00 | DNA Name Service Advertisement
> 09-00-2B-02-01-01 | 03-00-00-00-10-00 | DNA Name Service Solicit
> 09-00-2B-02-01-02 | 03-00-00-00-20-00 | DNA Time Service
> 03-00-00-00-00-01 | 03-00-00-00-00-01 | NETBUI Emulation
> 03-00-02-00-00-00 | 03-00-02-00-00-00 | RIPL

> #### /MAX_BUFFERS=value

> Sets the maximum number of receive buffers to be allocated and used by the LAN driver for the LAN device.

> Previous | Next | Contents | Index

> | privacy and legal statement |
> 6048PRO_031.HTML