LANCP> SET DEVICE/ALL/MIN_BUFFERS=12

This command sets the number of receive buffers for all LAN devices to be no less than 12.

LANCP> DEFINE DEVICE EXA0/MOPDLL=(ENABLE,EXCLUSIVE)

This command defines LAN device EXA0 to enable LANACP MOP downline load service in exclusive mode. The settings of the KNOWNCLIENTSONLY and SIZE characteristics are not changed. If the device entry does not currently exist in the LAN permanent device database, these settings will be set to the defaults.

LANCP> DEFINE DEVICE/ALL/MOPDLL=NOEXCLUSIVE

This command sets all LAN devices defined in the LAN permanent device database to nonexclusive mode for LANACP MOP downline load service.

LANCP> SET DEVICE EXA0/MOPDLL=(ENABLE,NOEXCLUSIVE) LANCP> SET DEVICE FXA0/MOPDLL=(ENABLE,EXCL,KNOWN)

These commands enable LANACP MOP downline load service for:

• LAN device EXA0 in nonexclusive mode
• LAN device FXA0 in exclusive mode for only known clients

LAN devices contain firmware images in EEPROM or FLASH ROM that you can update using the LANCP utility. You can update devices such as the DEMNA, DEMFA, DEFAA, DEFTA, DEFEA, and DEFPA.

On Alpha systems to update the firmware on a device, enter the UPDATE DEVICE command using the following syntax:

UPDATE DEVICE device-name [/qualifiers]

Table 22-10 provides a brief description of the UPDATE DEVICE command qualifiers.

Table 22-10 UPDATE DEVICE Command Qualifiers

Qualifier	Description
/FILE= filename	Provides the file specification of the file to be loaded into the device.
/RESET	Specifies whether the device will begin using the new image when the firmware update completes.

Example

LANCP> UPDATE DEVICE FAA0/FILE=DKA0:[FW]FBUS_MAIN.SYS

This command updates FDDI device FAA0 with the firmware image FBUS_MAIN.SYS located on DKA0:[FW]. The device begins using the new image after the firmware update has completed and a device reset has been done.

22.6 Managing the LAN Device Databases

The LAN volatile and permanent device databases contain a single entry for each LAN device that exists on the system. Each entry in the LAN volatile device database contains device information and MOP downline load counters information. Each entry in the LAN permanent device database contains device information that is used to populate the volatile database when the LANACP LAN server process is started.

Typically, each database contains the same devices. However, the permanent database may contain entries for devices that have not yet been configured or installed in the system. The LANACP LAN server process maintains the volatile device database. The LANCP utility maintains the permanent device database. You can manipulate either database using the LANCP utility commands depending on your user privileges, as follows:

• Privileged users can add or delete device entries from each database, enable or disable MOP downline load service, and clear MOP downline load counters information for LAN devices.
• Unprivileged users can view the MOP downline load status and counters information.

The following sections describe how to enter and remove devices from the LAN permanent and volatile device databases, and how to enable and disable MOP downline load services.

22.6.1 Displaying Devices in the LAN Device Databases

To display information in the LAN permanent device database, enter the LIST DEVICE command using the following syntax:

LIST DEVICE device-name [/qualifiers]

To display information in the LAN volatile device database, enter the SHOW DEVICE command using the following syntax:

SHOW DEVICE device-name [/qualifiers]

Table 22-11 provides a brief description of the LIST DEVICE and SHOW DEVICE qualifiers.

Table 22-11 LIST DEVICE and SHOW DEVICE Command Qualifiers

Qualifier	Description
/ALL	Lists, or shows all devices which match device names.
/CHARACTERISTICS	Same as the /PARAMETER qualifier.
/COUNTERS+	Displays device counters.
/DLL	Lists or shows downline load characteristics.
/MAP	Displays the current configuration of the functional address mapping table.
/MOPDLL	Same as DLL.
/OUTPUT= file-name	Creates the specified file and directs output to it.
/PARAMETERS	Displays status and related information about the device.
/REVISION+	Displays the current firmware revision of the adapter, if available or applicable.
/SR_ENTRY	Displays the contents of the current source routing cache table.

To enter a device into the LAN permanent device database or to modify an existing entry, enter the DEFINE DEVICE command using the following syntax:

DEFINE DEVICE device-name [/qualifiers]

To enter a device into the LAN volatile device database or to modify an existing entry, enter the SET DEVICE command using the following syntax:

SET DEVICE device-name [/qualifiers]

22.6.3 Deleting Devices from the LAN Device Databases

To delete a device from the LAN permanent device database, enter the PURGE DEVICE command using the following syntax:

PURGE DEVICE device-name [/ALL]

To delete a device from the LAN volatile device database, enter the CLEAR DEVICE command using the following syntax:

CLEAR DEVICE device-name [/ALL]

For the PURGE DEVICE and CLEAR DEVICE commands, the /ALL qualifier deletes all LAN devices in the LAN permanent device database.

Examples

1. LANCP> PURGE DEVICE/ALL

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

2. LANCP> CLEAR DEVICE EXA0

   
   This command deletes device EXA0 from the LAN volatile device database.

The LAN volatile and permanent node databases contain a single entry for each defined LAN node. Each entry in the LAN volatile node database contains node information and MOP downline load counters information. Each entry in the LAN permanent node database contains node information that is used to populate the volatile database when the LANACP LAN server process is started.

Typically, each database contains the same nodes. The LANACP LAN server process maintains the volatile node database. The LANCP utility maintains the permanent node database. You can manipulate either database using the LANCP utility commands depending on your user privileges, as follows:

• Privileged users can add or delete node entries from each database and clear MOP downline load counters information for LAN nodes
• Unprivileged users can view the node information and MOP downline load status and counters information

The following sections describe how to enter nodes into and remove nodes from the LAN permanent and volatile node databases.

22.7.1 Displaying Nodes in the LAN Node Databases

To display information in the LAN permanent node database, enter the LIST NODE command using the following syntax:

LIST NODE node-name [/ALL]

To display information in the LAN volatile node database, enter the SHOW NODE command using the following syntax:

SHOW NODE node-name [/ALL]

For the LIST NODE and SHOW NODE commands, the /ALL qualifier displays data for all nodes in the LAN permanent or volatile node database.

22.7.2 Entering Nodes into the LAN Node Databases

To enter a node into the LAN permanent node database or to modify an existing entry, enter the DEFINE NODE command using the following syntax:

DEFINE NODE node-name [/qualifiers]

To enter a node into the LAN volatile node database or to modify an existing entry, enter the SET NODE command using the following syntax:

SET NODE node-name [/qualifiers]

Table 22-12 provides a brief description of the DEFINE NODE and SET NODE command qualifiers.

Table 22-12 DEFINE NODE and SET NODE Command Qualifiers

Qualifier	Description
/ADDRESS= node-address	Associates a LAN address with the node name.
/ALL	Defines data for all nodes in the LAN permanent or volatile node database.
/BOOT_TYPE=VAX_SATELLITE| ALPHA_SATELLITE|OTHER	Indicates the type of processing required for downline load requests.
/FILE= file-spec	Supplies the file name you want to be provided when the downline load request does not include a file name.
/PERMANENT_DATABASE (SET command only)	Updates the node entries in the LAN volatile node database with any data currently set in the permanent database.
/ROOT= directory-specification	Supplies the directory specification to be associated with the file name.
/SIZE= value	Specifies the size in bytes of the file data portion of each downline load message.
/V3	Forces the server to respond to only MOP Version 3 boot requests from this node.
/VOLATILE_DATABASE (DEFINE command only)	Updates the node entries in the LAN permanent node database with any data currently set in the volatile database.

Examples

1. DEFINE NODE GALAXY/ADDRESS=08-00-2B-11-22-33 - /FILE=NISCS_LOAD.EXE - /ROOT=$64$DIA14:<SYS10.> - /BOOT_TYPE=VAX_SATELLITE

   
   This command sets up node GALAXY in the LAN permanent node database for booting as a VAX satellite into an OpenVMS Cluster system.
   The NISCS_LOAD.EXE file is actually located on
   $64$DIA14:<SYS10.SYSCOMMON.SYSLIB>. The <SYSCOMMON.SYSLIB> is supplied by the LANACP LAN server process and is not included in the root definition.

2. DEFINE NODE ZAPNOT/ADDRESS=08-00-2B-11-22-33 - /FILE=APB.EXE - /ROOT=$64$DIA14:<SYS10.> - /BOOT_TYPE=ALPHA_SATELLITE

   
   This command sets up node ZAPNOT for booting as an Alpha satellite into an OpenVMS Cluster system.
   The APB.EXE file is actually located on $64$DIA14:<SYS10.SYSCOMMON.SYSEXE>. Note that the <SYSCOMMON.SYSEXE> is supplied by the LANACP LAN server process and is not included in the root definition.

3. SET NODE CALPAL/ADDRESS=08-00-2B-11-22-33 - /FILE=APB_061.EXE

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

To delete a node from the LAN permanent node database, enter the PURGE NODE command using the following syntax:

PURGE NODE node-name [/ALL]

To delete a node from the LAN volatile node database, enter the CLEAR NODE command using the following syntax:

CLEAR NODE node-name [/ALL]

For the PURGE NODE and CLEAR NODE commands, the /ALL qualifier deletes all LAN nodes in the LAN permanent or volatile node database.

22.8 Understanding LAN MOP

The collection of utilities and startup command files for LANCP and LANACP provide the necessary functionality for MOP downline load service. These utilities and files load cluster satellites, terminal servers, and systems requiring downline load of special images, such as console update images or system software update images (for InfoServer load).

22.8.1 Coexistence with DECnet MOP

The LAN MOP environment provides functionality that is similar to that provided by DECnet. The result is that a system manager can choose which functionality to use, DECnet MOP or LAN MOP. For OpenVMS Cluster systems, LAN MOP permits the operation of a cluster without the presence of DECnet.

LAN MOP can coexist with DECnet MOP in the following ways:

• Running on different systems
  For example, DECnet MOP service is enabled on some of the systems on the LAN, and LAN MOP is enabled on other systems.
• Running on different LAN devices on the same system
  For example, DECnet MOP service is enabled on a subset of the available LAN devices on the system, and LAN MOP is enabled on the remainder.
• Running on the same LAN device on the same system but targeting a different set of nodes for service
  For example, both DECnet MOP and LAN MOP are enabled, but LAN MOP has limited the nodes to which it will respond. This allows DECnet MOP to respond to the remainder.

To migrate to LAN MOP, follow these steps:

1. Decide which nodes are to provide MOP downline load service. These may be the same nodes that currently have service enabled for DECnet.
2. Populate the LAN permanent device database by typing the following command at the DCL prompt:

   MCR LANCP DEFINE DEVICE/UPDATE

3. Populate the LAN permanent node database by entering a node definition for each cluster satellite node and any other nodes that are similarly defined in the DECnet node database. You can enter this data manually or execute the command procedure SYS$EXAMPLES:LAN$POPULATE.COM, following the directions and help provided.
4. Disable service on each of the DECnet circuits where it is currently enabled in the volatile database.
5. Enable service on each LAN device in the LAN permanent device database that you would like to use by typing the following command at the DCL prompt for each device:

   MCR LANCP DEFINE DEVICE device-name/MOPDLL=ENABLE

6. If high performance is required, select a data size of 1482 bytes and only reduce this if some load requests now fail. Alternatively, set up one system to load those clients that require a small data size and set up a different system to load the other clients.

To permanently migrate back to DECnet MOP, follow these steps:

1. Disable the MOP service in the volatile database by typing the following:

   MCR LANCP SET DEVICE device-name/MOPDLL=DISABLE

2. Disable the MOP service in LANCP's permanent database by typing the following:

   MCR LANCP DEFINE DEVICE device-name/MOPDLL=DISABLE

3. Reenable service on each DECnet circuit in the permanent and volatile databases.

A cluster management command procedure has been provided to facilitate the use of LANCP for LAN MOP booting of satellites. Called CLUSTER_CONFIG_LAN.COM, it resides in SYS$MANAGER and is a direct parallel to CLUSTER_CONFIG.COM, which is used by cluster managers to configure and reconfigure an OpenVMS Cluster system. The two procedures perform the same functions, but CLUSTER_CONFIG.COM uses DECnet MOP for downline load, whereas CLUSTER_CONFIG_LAN.COM uses LAN MOP and does not use DECnet for anything. Therefore, when you add a new node, CLUSTER_CONFIG_LAN.COM does not ask for the node's DECnet node name and address. Instead, it queries for an SCS node name and an SCS node ID number.

For your convenience, you can still run CLUSTER_CONFIG.COM. When you execute CLUSTER_CONFIG.COM, it checks whether LANACP for MOP booting is also running. It also checks to see if DECnet is running. If LANACP is running and DECnet is not, then CLUSTER_CONFIG.COM dispatches to CLUSTER_CONFIG_LAN.COM. If CLUSTER_CONFIG.COM discovers that both LANACP and DECnet are running, it asks the user whether LAN MOP booting is being used, and whether it should call CLUSTER_CONFIG_LAN.COM for the user.

22.8.4 Sample Satellite Load

The following example shows how to issue commands to the LANCP utility to enable MOP downline load service and to define node ZAPNOT:

set acp/opcom set device eza0/mopdll=enable set node ZAPNOT/addr=08-00-2B-33-FB-F2/file=APB.EXE- /root=$64$DIA24:<SYS11.>/boot=Alpha

The following example shows the OPCOM messages displayed when you start up the LANACP LAN server process:

%%%%%%%%%%% OPCOM 10-JUN-1998 06:47:35.18 %%%%%%%%%%% Message from user SYSTEM on GALAXY LANACP MOP Downline Load Service Found LAN device EZA0, hardware address 08-00-2B-30-8D-1C %%%%%%%%%%% OPCOM 10-JUN-1998 06:47:35.25 %%%%%%%%%%% Message from user SYSTEM on GALAXY LANACP MOP Downline Load Service Found LAN device EZB0, hardware address 08-00-2B-30-8D-1D %%%%%%%%%%% OPCOM 10-JUN-1998 06:47:54.80 %%%%%%%%%%% Message from user SYSTEM on GALAXY LANACP MOP V3 Downline Load Service Volunteered to load request on EZA0 from ZAPNOT Requested file: $64$DIA24:<SYS11.>[SYSCOMMON.SYSEXE]APB.EXE %%%%%%%%%%% OPCOM 10-JUN-1998 06:48:02.38 %%%%%%%%%%% Message from user SYSTEM on GALAXY LANACP MOP V3 Downline Load Service Load succeeded for ZAPNOT on EZA0 System image, $64$DIA24:<SYS11.>[SYSCOMMON.SYSEXE]APB.EXE (Alpha image)

The following display shows the contents of the LAN$ACP.LOG file:

10-JUN-1998 06:47:35.02 Found LAN device EZA0, hardware address 08-00-2B-30-8D-1C 10-JUN-1998 06:47:35.18 Found LAN device EZB0, hardware address 08-00-2B-30-8D-1D 10-JUN-1998 06:47:35.25 LANACP initialization complete 10-JUN-1998 06:47:45.39 Enabled LAN device EZA0 for MOP downline load service in exclusive mode 10-JUN-1998 06:47:54.70 Volunteered to load request on EZA0 from ZAPNOT Requested file: $64$DIA24:<SYS11.>[SYSCOMMON.SYSEXE]APB.EXE 10-JUN-1998 06:48:02.23 Load succeeded for ZAPNOT on EZA0 MOP V3 format, System image, $64$DIA24:<SYS11.>[SYSCOMMON.SYSEXE]APB.EXE Packets: 2063 sent, 2063 received Bytes: 519416 sent, 4126 received, 507038 loaded Elapsed time: 00:00:07.42, 68276 bytes/second

	privacy and legal statement
6017PRO_093.HTML