HP OpenVMS System Manager's Manual, Volume 2:...

Managing the Local Area Network (LAN) Software

Managing the LAN Device Databases

Understanding LAN MOP

Managing the LAN Node Databases  

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.

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.

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]

DEFINE NODE and SET NODE Command Qualifiers provides a brief description of the DEFINE NODE and SET NODE command qualifiers.

Table 16   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 NODE 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.

Deleting Nodes from the LAN Node Databases  

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.

Managing the LAN Device Databases

Understanding LAN MOP