Document revision date: 19 July 1999

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.

22.9 Managing the LAN MOP Downline Load Service

The LANACP LAN server process maintains the LAN volatile node and device databases. The LANCP utility provides commands that:

• Display MOP downline load status and counters information
• Clear counters information
• Enable or disable OPCOM messages and packet tracing

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.

22.9.1 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 Section 22.6.2 for a complete description of this command.

22.9.2 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 Section 22.6.2 for a complete description of this command.

22.9.3 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-JUN-1998 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

22.9.4 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]

Table 22-13 provides a brief description of the LIST NODE and SHOW NODE command qualifiers.

Table 22-13 LIST NODE and SHOW NODE Command Qualifiers

Qualifier	Description
/ALL	Displays information for all nodes in the database.
/OUTPUT= file-name	Indicates that the output should be directed to the specified file. If the file name extension is .com, then 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.
/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:

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

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

22.9.5 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

22.9.6 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

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

1. Receive a Program Request message on the Load Assistance Multicast Address from the requesting node, code 8.
2. Transmit an Assistance Volunteer message to the requesting node, code 3.
3. Receive a Program Request message on your node address from the requesting node, code 8.
4. Transmit a Memory Load message to the requesting node with sequence number zero, code 2.
5. Receive a Request Memory Load message requesting the next sequence number (modulo 256), code 10 (decimal).
6. Repeat steps 4 and 5 until there is no more data to send.
7. Transmit a Memory or Parameter Load with Transfer Address message, code 0 or 20 (decimal).
8. Receive a final Request Memory Load message requesting the next sequence number (modulo 256) indicating that the last message has been received, code 10 (decimal).

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

22.9.8 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]

Table 22-14 provides a brief description of the CONNECT NODE command qualifiers.

Table 22-14 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

1. CONNECT NODE GALAXY/DEVICE=EWA0

   
   This command attempts a console carrier connection to node GALAXY using the Ethernet device EWA0.

2. CONNECT NODE 08-00-2B-11-22-33/DEVICE=EWA0/PASSWORD=0123456789ABCDEF

   
   This command attempts a console carrier connection to the given node address using the Ethernet device EWA0, with a password.

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-15 provides a brief description of the TRIGGER NODE command qualifiers.

Table 22-15 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

1. TRIGGER NODE GALAXY/DEVICE=EWA0

   
   This command sends MOP trigger boot messages to node GALAXY using Ethernet device EWA0.

2. TRIGGER NODE 08-00-2B-11-22-33/DEVICE=EWA0/PASSWORD=0123456789ABCDEF

   
   This command sends MOP trigger boot messages to the given node address using the Ethernet device EWA0, with indicated password.

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

This chapter describes the following tasks:

Task	Section
Establishing a server management session	Section 23.3
Starting InfoServer Client for OpenVMS software automatically	Section 23.5.3
Making InfoServer devices available automatically	Section 23.6.3

This chapter explains the following concepts:

Concept	Section
InfoServer functions	Section 23.1
LASTport protocols	Section 23.2
InfoServer Client for OpenVMS functions	Section 23.4
LASTCP utility functions	Section 23.5
LADCP utility functions	Section 23.6

23.1 Understanding InfoServer Functions

The InfoServer system is a high-performance virtual device server. It can make available, or serve, compact discs, read/write disks, magneto-optical (MO) devices, and tapes to client systems on the local area network (LAN). Systems running InfoServer Client software can connect to the virtual devices and use them as though they are locally attached devices.

Unlike a file server, the InfoServer system does not impose a file system on the virtual devices that it serves. For example, the InfoServer system can serve a disk with any type of on-disk file structure. The client system interprets the on-disk structure and uses its own native file system to access data. Multiple on-disk structures can be served by and accessed on a single InfoServer system at the same time.

The InfoServer system can perform the following functions:

• Serve compact discs
  The InfoServer system serves compact discs automatically, using a disc's volume label as the service name when the server is booted or when a disc is inserted into an InfoServer drive. You do not have to perform any management action. Client systems simply bind to and mount the disc under its volume label.
  The InfoServer system can automatically serve to OpenVMS clients compact discs that are in ODS-2 format. High Sierra and ISO-9660 compact discs and other media types can be served manually through the InfoServer management interface.
• Serve Small Computer System Interface (SCSI) tapes
  Using service names, the InfoServer system can serve SCSI tape devices to the network. Client systems can connect to these tape devices and use them as though they were locally attached devices.
• Serve read/write disk partitions
  A partition is a logical subset of an InfoServer read/write disk. A single disk can be subdivided into several partitions, each of which can be served to the network independently. To remote client systems, these partitions appear to be whole disks. For example, a client system using InfoServer Client for OpenVMS software can access the partitions and use them as though they are local hard disks.
• Act as an initial load system for OpenVMS systems
  The InfoServer system can downline load the primary bootstrap program to OpenVMS systems by responding to Maintenance Operation Protocol (MOP) requests. The server can locate MOP downline load files on the OpenVMS software distribution compact disc and copy them into temporary MOP partitions on an InfoServer-formatted read/write disk.
  The initial system load (ISL) bootstrap program connects back to the software distribution compact disc and boots Standalone Backup. The Backup utility is then used to copy the OpenVMS operating system save sets from the compact disc to a read/write disk attached to the system. All subsequent OpenVMS boots are done from the local read/write disk.
• Downline load other products
  You can use the InfoServer system to load any Ethernet product by file name; that is, the server does not require a Network Control Program (NCP) database entry to locate the requested file. For example, X terminal clients use the InfoServer system to downline load their system software. You can create a special MOP partition and copy the desired file to that partition. The server additionally supports downline loading of services by Ethernet address. Each InfoServer system can handle up to 100 simultaneous downline loads more efficiently than host-based downline loaders, which must start processes to assist in the load.

Figure 23-1 shows the relationship of the InfoServer system to several possible client systems. In this figure, two compact discs and two hard disks connected to the server appear to the client systems as local devices. The VAX system and the RISC workstation might be using one or two of the compact discs for software distribution and online documentation, while the PC might be referencing a disk partition on the InfoServer system. The X terminal boots from the InfoServer system and uses InfoServer disks for page, font, and customization files.

Figure 23-1 InfoServer System Serving Clients

You can connect the InfoServer system to your Ethernet LAN and turn on the system. After the server is initialized, or bootstrapped, the server software automatically serves to client systems the device media connected to it. If you insert a compact disc into a server drive, the server detects this new device and automatically serves it to client systems by using the volume label as the service name.

The server bootstraps from its internal read/write device, on which the InfoServer software is preinstalled. InfoServer software updates are distributed on compact discs. As these new releases become available, you can install the software onto the internal device for subsequent booting. To update InfoServer software from the compact disc, follow these steps:

1. Insert the disc in a compact disc drive attached to the InfoServer system.
2. Move the InfoServer software to the internal read/write device. At the InfoServer prompt, enter a command in the following format, where n is the drive number:
   On the InfoServer 100 or InfoServer 150 system:

   InfoServer> UPDATE SYSTEM DKn:

   
   On the InfoServer 1000 system:

   InfoServer> UPDATE SYSTEM DKn: FLASH

   
   The next time you boot the InfoServer system, it runs the updated software.

You can use the Software Products Library (formerly known as ConDIST) to update InfoServer software. After you log in to the InfoServer system, perform the following steps:

1. Insert the disk containing the [INFOSERVxxx] directory tree in a compact disk drive attached to the InfoServer system.
2. At the InfoServer> prompt, enter a command in the following format, where n is the drive number:
   • On the InfoServer 100 or InfoServer 150 system, enter a command in the following format:

     UPDATE SYSTEM DKn:

   • On the InfoServer 1000 system, enter a command in the following format:

     UPDATE SYSTEM DKn: FLASH

   
   These commands move the InfoServer software to the internal read/write device. The next time you boot the InfoServer system, it runs the updated software. Note that you can also boot the server from the Software Products Library disk.

You might want to customize server features. You can control InfoServer functions by logging in to the server and entering server commands, described in detail in the InfoServer System Operations Guide.

	privacy and legal statement
6017PRO_094.HTML