HP OpenVMS Systems Documentation

HP OpenVMS System Management Utilities Reference Manual

The command in this example replaces the known image GRPCOMM with the latest version of the image, while enabling image accounting and removing the OPEN attribute from this version.

The full name of the file specification is assumed to be SYS$SYSTEM:GRPCOMM.EXE.

12.1 LANCP Description

You can use LANCP to:

• Obtain LAN device counters, revision, and configuration information
• Change the operational parameters of LAN devices on the system
• Maintain the LAN permanent and volatile device and node databases
• Control the LANACP LAN Server process (including Maintenance Operations Protocol (MOP) downline load server related functions)
• Initiate MOP console carrier and MOP trigger boot operations

On VAX systems, LANCP and LANACP are limited to the display of LAN counters and configuration data, maintenance of the node and device databases, and control of MOP functions.

On Alpha and I64 systems, LANCP and LANACP functionality is equivalent. On I64, however, FDDI, Token Ring, and ATM are not supported; therefore, the commands involving these devices are not relevant.

12.2 LANCP Usage Summary

You can use the LANCP utility to:

• Set LAN parameters to customize your LAN environment.
• Display LAN settings and counters.
• Provide MOP downline load support for devices such as terminal servers, x-terminals, and LAN-based printers, and for booting satellites in an OpenVMS Cluster environment.

Format

LANCP [command]

Parameter

command

Specifies a LANCP command. This parameter is optional. If no command is specified, the utility displays its prompt and waits for command input.

Description

To invoke LANCP, enter the following command at the DCL command prompt:

$ RUN SYS$SYSTEM:LANCP

The LANCP utility responds by displaying the LANCP> prompt, at which you can enter any LANCP command described in this chapter.

To define LANCP as a foreign command, either at the DCL prompt or in a startup or login command file, enter:

$ LANCP :== $SYS$SYSTEM:LANCP

Then you can enter the LANCP command at the DCL prompt to invoke the utility and enter LANCP commands.

When you enter the LANCP command:

• Without specifying any command qualifiers, the LANCP utility displays the LANCP> prompt, at which you can enter commands.
• With command qualifiers, the LANCP utility terminates after it executes the command and returns you to the DCL command prompt.

Note Some LANCP commands require special privileges.

To exit from the LANCP utility, enter the EXIT command at the LANCP> prompt or press Ctrl/Z.

For information about the LANCP utility, enter the HELP command at the LANCP> prompt.

This section describes and provides examples of the LANCP commands. The following table summarizes the LANCP commands:

Executes a command procedure or requests the command interpreter to read subsequent command input from a specific file or device.

Format

@ file-spec

Parameter

file-spec

Specifies either the input device or the file for the preceding command, or the command procedure to be executed.

Qualifiers

None.

Example

$ CREATE COUNT.COM
SHOW DEVICE/COUNTERS EIA
SPAWN WAIT 00:01:00
@COUNT
[Ctrl/Z]
$ RUN SYS$SYSTEM:LANCP
LANCP> @COUNT

Device Counters EIA0:
   Value  Counter
   -----  -------
   62030 Seconds since last zeroed
19910982 Bytes received
  239192 Bytes sent
  155812 Packets received
    4348 Packets sent
19910982 Multicast bytes received
  239140 Multicast bytes sent
  155812 Multicast packets received
    4346 Multicast packets sent
       0 Unrecognized unicast destination packets
  134311 Unrecognized multicast destination packets
       0 Unavailable station buffers
       0 Unavailable user buffers
       0 Alignment errors
       0 Frame check errors
       0 Frame size errors
       0 Frame status errors
       0 Frame length errors
       0 Frame too long errors
       0 Data overruns
       0 Send data length errors
       0 Receive data length errors
       0 Transmit underrun errors
       0 Transmit failures
       0 Carrier check failures
       0 Station failures
       0 Initially deferred packets sent
       0 Single collision packets sent
       0 Multiple collision packets sent
       0 Excessive collisions
       0 Late collisions
       0 Collision detect check failures
       1 Link up transitions (19-OCT-2004 13:47:50.86)
       0 Link down transitions
    None Time of last generic transmit error
    None Time of last generic receive error


      

This example creates and runs a command procedure, COUNT.COM, that displays device counters once every minute.

Deletes device data from the LAN volatile device database. Requires SYSPRV privilege.

Format

CLEAR DEVICE device-name

Parameter

device-name

Supplies the LAN controller device name. The device name has the form ddcu where dd is the device code, c is the controller designation, and u is the unit number.

LAN devices are specified as the name of the template device, which is unit 0. For example, the first PCI Ethernet device is specified as EWA0, the second as EWB0., and so on. You can, for example, specify a DEMNA controller as EXA, EXA0, or EXA0:.

Qualifier

/ALL

Deletes data for all LAN devices in the LAN volatile device database. If you specify a device name, all matching LAN devices are selected. For example: E to select all Ethernet devices, F for FDDI, I for Token Ring, EW to select all PCI Ethernet PCI devices.

/CHARACTERISTICS or /PARAMETERS

Deletes device characteristics settings for the LAN device, such as speed, duplex mode, and other device parameters.

/DLL or /MOPDLL

Deletes MOP downline load settings for the LAN device.

/TRACE

Deletes driver tracing settings for the LAN device.

If no qualifier is present to select the type of data to delete, the entire device entry is deleted.

Example

LANCP> CLEAR DEVICE EXA0
      

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

This command clears MOP downline load counters from the LAN volatile device and node databases for all nodes and devices. This command requires SYSPRV privilege.

Format

CLEAR DLL

Parameters

None.

Qualifiers

None.

Example

LANCP> CLEAR DLL

      

This command clears MOP downline load counters from the LAN volatile device and node databases for all nodes and devices.

Deletes a node from the LAN volatile node database. Requires SYSPRV privilege.

Format

CLEAR NODE node-name

Parameter

node-name

Supplies the name of a node in the LAN volatile node database.

Qualifier

/ALL

Deletes all LAN nodes in the LAN volatile node database. If you specify a node name, all matching nodes are selected; for example, A/ALL deletes all nodes whose name begins with A.

Example

LANCP> CLEAR NODE VAXSYS

      

This command deletes the node VAXSYS from the LAN volatile node database.

Opens a MOP console carrier connection to the specified node. This allows a local terminal to act as the console for a remote system.

Format

CONNECT NODE node-specification

Parameter

node-specification

Supplies either the node name or the node address of the target node. If you supply the node name, the node address is obtained by looking up the node name in the LAN volatile node database. If you supply the node address, the corresponding node need not be defined in the LAN volatile node database. The canonical form of the address consists of 6 hexadecimal byte characters separated by hyphens. Use a colon as the separator character to indicate the bit-reversed form of the address.

Qualifiers

/DEVICE=device-name

Specifies the LAN controller device name to be used for the connection. For example, you can specify a DEMNA controller as EXA, EXA0, or EXA0:.

/DISCONNECT=disconnect-character

Specifies a character that you can use to terminate the connection to the remote node. To terminate a connection, press Ctrl/disconnect-character. You can select any ASCII character from @ through Z, except C, M, Q, S, Y; the default disconnect character is D.

/PASSWORD=16hexdigits

Supplies the password to be used when the connection is initiated, in hexadecimal (for example, /PASSWORD=0123456789ABCDEF). The default password is zero. You can omit leading zeros.

/V3 or /V4

Indicates that MOP Version 3 or Version 4 formatted messages, respectively, are to be used to make the connection. By default, LANCP determines the format by sending MOP Request ID messages to the remote node first in MOP Version 4 format, then in Version 3 format, repeating this process until a response is received or timeout occurs.

You can specify the format:

• To allow connection to nodes that do not support Request ID messages
• As a means of getting around implementation problems with one of the formats

Examples

LANCP> CONNECT NODE GALAXY/DEVICE=EWA0
      

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

LANCP> CONNECT NODE 08-00-2B-11-22-33/DEVICE=EWA0/PASSWORD=0123456789AB
      

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

Converts the device database to the format required by LANCP. If the database is not updated, LANCP can read the database but not update entries in it. The conversion is necessary when the contents of the device entry changes from one OpenVMS release to the next. Requires SYSPRV privilege.

Format

CONVERT DEVICE_DATABASE device_database

Parameters

None.

Qualifiers

None.

Converts the node database to the format required by LANCP. If the database is not updated, LANCP can read the database but not update entries in it. The conversion is necessary when the contents of the node entry changes from one OpenVMS release to the next. Requires SYSPRV privilege.

Format

CONVERT NODE_DATABASE node_database

Parameters

None.

Qualifiers

None.

Enters a device into the LAN permanent device database or modifies an existing entry. Requires SYSPRV privilege.

QUALIFIERS See the SET DEVICE command for a list of qualifiers and the description of each. Except where noted, the only difference is that DEFINE DEVICE applies to entries in the LAN permanent device database rather than the volatile device database.

Format

DEFINE DEVICE device-name

Parameter

device-name

Supplies the name of a device to be added to the LAN permanent device database or an entry to be modified. The device name has the form ddcu where dd is the device code, c is the controller designation, and u is the unit number. LAN devices are specified as the name of the template device, which is unit 0; for example, the first PCI Ethernet device is specified as EWA0, the second as EWB0.

Examples

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

This command defines LAN device EXA0 to enable LANACP MOP downline load service in exclusive mode. The setting 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 are 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> DEFINE DEVICE/ALL/UPDATE/VOLATILE_DATABASE
      

This command enters all Ethernet devices into the LAN permanent device database and updates the entry to include the current parameter values.

Enters a node into the LAN permanent node database or modifies an existing entry. Requires SYSPRV privilege.

QUALIFIERS See the SET NODE command for a list of qualifiers and the description of each. Except where noted, the only difference is that DEFINE NODE applies to entries in the LAN permanent node database rather than the volatile node database.

Format

DEFINE NODE node-name

Parameter

node-name

Supplies the name of a node to be added to the LAN permanent node database or an entry to be modified. Typically, the node name is the same as that given in the system parameter SCSNODE, but it does not need to be. The node name is limited to 63 characters in length.

Examples

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

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.

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

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.

LANCP> DEFINE 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 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.