|
HP OpenVMS System Manager's Manual, Volume 2:... |
Managing the Local Area Network (LAN) Software |
|
|
| |
Managing the LAN MOP Downline Load Service
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.
Enabling MOP Downline Load Service
To enable MOP downline load service, enter the SET DEVICE
command using the following syntax: SET DEVICE device-name/DLL=ENABLE
In this command, use the device-name parameter to supply the LAN controller device name.
See Entering Devices into the LAN Device Databases for a complete description of this command.
Disabling MOP Downline Load Service
To disable MOP downline load service, enter the SET DEVICE
command using the following syntax:SET DEVICE device-name/DLL=DISABLE
In this command, use the device-name parameter to supply the LAN controller device name.
See Entering Devices into the LAN Device Databases for a complete description of this command.
Displaying the Status and Counters Data
To display MOP downline load status, enter the SHOW DLL command
using the following syntax:SHOW DLL
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-JAN-2004 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
Displaying the Status and Counters Data for
Individual Nodes
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]
LIST NODE and SHOW NODE Command Qualifiers provides a brief description of the LIST NODE and SHOW NODE command qualifiers.
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-jan-2001 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-jan-2004 09:11:17.29
Clearing the Counters Data
To clear MOP downline load counters for all nodes and devices,
enter the CLEAR DLL command using the following syntax: CLEAR DLL
OPCOM Messages
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
Load Trace Facility
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
MOP Console Carrier
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]
CONNECT NODE Command Qualifiers provides a brief description of the CONNECT NODE command qualifiers.
CONNECT NODE GALAXY/DEVICE=EWA0CONNECT NODE 08-00-2B-11-22-33/DEVICE=EWA0/PASSWORD=0123456789ABCDEFMOP Trigger Boot
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]
TRIGGER NODE Command Qualifiers provides a brief description of the TRIGGER NODE command qualifiers.
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:
TRIGGER NODE GALAXY/DEVICE=EWA0TRIGGER NODE 08-00-2B-11-22-33/DEVICE=EWA0/PASSWORD=0123456789ABCDEF
|
|