![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
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
LANCP> PURGE DEVICE/ALL
LANCP> CLEAR DEVICE EXA0
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:
The following sections describe how to enter nodes into and remove nodes from the LAN permanent and volatile 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.
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-13 provides a brief description of the 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
DEFINE NODE GALAXY/ADDRESS=08-00-2B-11-22-33 -
/FILE=NISCS_LOAD.EXE -
/ROOT=$64$DIA14:<SYS10.> -
/BOOT_TYPE=VAX_SATELLITE
DEFINE NODE ZAPNOT/ADDRESS=08-00-2B-11-22-33 -
/FILE=APB.EXE -
/ROOT=$64$DIA14:<SYS10.> -
/BOOT_TYPE=ALPHA_SATELLITE
SET NODE CALPAL/ADDRESS=08-00-2B-11-22-33 -
/FILE=APB_061.EXE
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.
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).
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:
To migrate to LAN MOP, follow these steps:
MCR LANCP DEFINE DEVICE/UPDATE
MCR LANCP DEFINE DEVICE device-name/MOPDLL=ENABLE
@SYS$STARTUP:LAN$STARTUP
To migrate permanently, follow these steps:
To migrate back to DECnet MOP, follow these steps:
SET ACP/STOP
Note
Any nodes that you added while booting with LAN MOP will not have been entered in the DECnet node database as targets for downline load, and they will need to be updated when you return to DECnet MOP.
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.
The following 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 shows the OPCOM messages displayed when you start up the LANACP LAN server process:
%%%%%%%%%%% OPCOM 10-JUN-1996 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-1996 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-1996 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-1996 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-1996 06:47:35.02 Found LAN device EZA0, hardware address
08-00-2B-30-8D-1C
10-JUN-1996 06:47:35.18 Found LAN device EZB0, hardware address
08-00-2B-30-8D-1D
10-JUN-1996 06:47:35.25 LANACP initialization complete
10-JUN-1996 06:47:45.39 Enabled LAN device EZA0 for MOP downline load service in
exclusive mode
10-JUN-1996 06:47:54.70 Volunteered to load request on EZA0 from ZAPNOT
Requested file: $64$DIA24:<SYS11.>[SYSCOMMON.SYSEXE]APB.EXE
10-JUN-1996 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
The LAN enhancements permit cross-architecture booting in a OPENVMS Cluster system. VAX boot nodes can provide boot service to Alpha satellites, and Alpha boot nodes can provide boot service to VAX satellites. Note that each architecture must include a system disk that is used for installations and upgrades.
The LANACP LAN server process maintains the LAN volatile node and device databases. The LANCP utility provides commands that:
Counters and status information is maintained for each node and device. Counters information includes transmitted and received byte and packet counts, transmit errors, logical errors such as protocol violations and timeouts, and number of load requests. Status includes the time of the last load and the status of the last load.
To enable MOP downline load service, enter the SET DEVICE command using the following syntax:
SET DEVICE device-name/MOPDLL=ENABLE
In this command, use the device-name parameter to supply the LAN controller device name.
See Section 22.6.2 for a complete description of this command.
To disable MOP downline load service, enter the SET DEVICE command using the following syntax:
SET DEVICE device-name/MOPDLL=DISABLE
In this command, use the device-name parameter to supply the LAN controller device name.
See Section 22.6.2 for a complete description of this command.
To display MOP downline load status, enter the SHOW MOPDLL command using the following syntax:
SHOW MOPDLL
The following display shows counters information for a particular node:
LAN MOP DLL Status:
EXA enabled in exclusive mode for known nodes only, data size 1482 bytes
FXA disabled
#Loads Packets Bytes Last load time Last loaded
------ ------- ----- -------------------- -----------------
EXA 5 1675 4400620 10-JUN-1996 10:27.51 GALAXY
FXA 0 0 0
On this node are two LAN devices, EXA (DEMNA) and FXA (DEMFA). MOP downline load service is enabled on EXA in exclusive mode.
Requests are answered only for nodes that are defined in the LANACP node database. The image data size in the load messages is 1482 bytes. There have been five downline loads, the last one occurring on node GALAXY at 10:27. Finally, no downline loads are recorded for FXA, which is currently disabled for downline load service.
To display recent downline load activity that has been logged in the LAN$ACP.LOG file, enter the SHOW LOG command using the following syntax:
SHOW LOG
To display MOP downline load information for nodes in the LAN permanent node database, enter the LIST NODE command using the following syntax:
LIST NODE node-name [/qualifiers]
To display MOP downline load status and counters information for nodes in the LAN volatile node database, enter the SHOW NODE command using the following syntax:
SHOW NODE node-name [/qualifiers]
Table 22-14 provides a brief description of the LIST NODE and SHOW NODE command qualifiers.
| Qualifier | Description |
|---|---|
| /ALL | Displays information for all nodes in the database. |
| /OUTPUT= command-file-name | Indicates that the output should be directed to the specified file 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. |
| /TOTAL (SHOW NODE command only) | Displays counter totals only. |
Example
The following example shows output from a command issued on a local node on which there are three nodes defined (GALAXY, ZAPNOT, and CALPAL). CALPAL has issued two load requests:
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-1996 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-1996 09:11:17.29
To clear MOP downline load counters for all nodes and devices, enter the CLEAR MOPDLL command using the following syntax:
CLEAR MOPDLL
By default, OPCOM messages are enabled. Messages are generated by the LANACP LAN server process when 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.
To enable OPCOM messages, enter the SET ACP/OPCOM command using the following syntax:
SET ACP/OPCOM
If the error data produced by the LANACP LAN server process for a load request is not sufficient to help you determine why the load is failing, you can direct the server process to record trace data. The data consists of transmit and receive packet information for every transmit and receive done by the server, and written to a log file for each load attempt. The name of the log file is SYS$MANAGER:LAN$nodename.LOG. You can record either all packet data or only the first 32 bytes of each packet.
The following list describes the typical load sequence:
For cluster satellite loads, the last Memory Load message contains cluster parameters. This message and the final Load with Transfer Address messages are displayed in full even if only partial trace echo has been enabled.
To enable partial tracing of packet data, enter the SET ACP/ECHO command using the following syntax:
SET ACP/ECHO
To enable full tracing of packet data, add the /FULL qualifier:
SET ACP/ECHO/FULL
Console carrier provides a mechanism to connect to a LAN device, such as a terminal server, that implements a management interface using the MOP console carrier protocol. The LANCP utility provides this function in the form of a CONNECT NODE command.
The command syntax is:
CONNECT NODE node-specification [/qualifiers]
Table 22-15 provides a brief description of the CONNECT NODE command qualifiers.
| Qualifier | Description |
|---|---|
| /DEVICE= device-name | Specifies the LAN controller device name to be used for the connection. |
| /DISCONNECT= disconnect-character | Specifies a character that you can use to terminate the connection to the remote node. |
| /PASSWORD=16hexdigits | Supplies the password to be used when the connection is initiated. |
| /V3 or /V4 | Indicates that MOP Version 3 or Version 4 formatted messages, respectively, are to be used to make the connection. |
Examples
CONNECT NODE GALAXY/DEVICE=EWA0
CONNECT NODE 08-00-2B-11-22-33/DEVICE=EWA0/PASSWORD=0123456789ABCDEF
Some systems recognize and respond to MOP remote boot requests. These systems typically require a password or other mechanism to prevent unwanted boot requests from triggering a reboot of the system. The LANCP utility provides this function in the form of the TRIGGER NODE command.
To request a reboot of a LAN system, enter the TRIGGER NODE command using the following syntax:
TRIGGER NODE node-specification [/qualifiers]
Table 22-16 provides a brief description of the TRIGGER NODE command qualifiers.
| Qualifier | Description |
|---|---|
| /DEVICE= device-name | Specifies the LAN controller device name to be used for sending the boot messages. |
| /PASSWORD=16hexdigits | Supplies the password to be used when the connection is initiated. |
Rather than specify the format to send MOP Version 3 or 4, the LANCP utility sends one message in each format to the target node.
The following examples show how to use the TRIGGER NODE command:
Examples
TRIGGER NODE GALAXY/DEVICE=EWA0
TRIGGER NODE 08-00-2B-11-22-33/DEVICE=EWA0/PASSWORD=0123456789ABCDEF
This chapter describes InfoServer functions and InfoServer Client for OpenVMS software, which enables OpenVMS systems to access InfoServer device services. The chapter also describes the tasks you must perform to start the client software on your system and to make InfoServer devices available as public devices.
Information Provided in This Chapter
6017P068.HTM OSSG Documentation 22-NOV-1996 14:22:57.41
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.