![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
This chapter describes the following tasks:
| Task | Section |
|---|---|
| Running the LANACP LAN server process | Section 22.3.1 |
| Invoking and running LANCP | Section 22.4.1 |
| Managing LAN devices | Section 22.5 |
| Managing the LAN device databases | Section 22.6 |
| Managing the LAN node databases | Section 22.7 |
| Migrating from DECnet MOP to LAN MOP | Section 22.8.2 |
| Using CLUSTER_CONFIG_LAN.COM and LAN MOP | Section 22.8.3 |
| Managing the MOP downline load services | Section 22.9 |
| Initiating the MOP console carrier | Section 22.9.8 |
| Requesting MOP trigger boot | Section 22.9.9 |
This chapter explains the following concepts:
| Concept | Section |
|---|---|
| Local area networks | Section 22.1 |
| LANACP LAN server process | Section 22.3 |
| LANCP utility | Section 22.4 |
| MOP downline load services | Section 22.8 |
A local area network (LAN) provides a communications channel designed to connect information processing equipment in a limited area such as a room, a building, or a complex of buildings (for example, a campus). Nodes in a LAN can be linked by the following types of data transmission media:
LAN controllers are devices that, along with additional external hardware, implement the Ethernet, FDDI, Token Ring, LAN emulation over ATM or Classical IP (RFC 1577) specifications. A LAN controller and the local system constitute a node. The LAN controller communicates with the local system through the system bus, and with remote systems implementing the Ethernet, FDDI, Token Ring, or LAN emulation over ATM specifications through the communication medium. (The Ethernet specification is described in The Ethernet--Data Link Layer and Physical Layer Specification. The FDDI specifications are available from ANSI. The Token Ring specifications are available from IEEE. The LAN emulation over ATM specifications are available from the ATM Forum.)
Application programs use the LAN driver's QIO interface to perform I/O operations to and from other nodes on the LAN. For detailed information on the QIO interface, see the OpenVMS I/O User's Reference Manual.
Table 22-1 provides a brief summary of the differences between the types of LAN media.
| Characteristic | Ethernet/802.3 | FDDI | Token Ring/802.5 ++ | LAN emulation over ATM++ |
|---|---|---|---|---|
| Speed | 10 Mb/s | 100 Mb/s | 4 or 16 Mb/s | 155Mb/s |
| Max. Frame Size | 1518 bytes | 4500 bytes | 4500 or 17,800 bytes | 1516, 4544, or 9234 |
| Max. Stations | 1024 | 500 | 260 | LAN server determines number of stations supported |
| Max. LAN Size | 2.8 km | 100 km | 300 m | Unrestricted |
Ethernet controllers use a single multiaccess channel with CSMA/CD to provide direct access from the processor to the Ethernet. On the Ethernet, all nodes have equal access.
An Ethernet is a cable to which each system or device is connected by a single line. In an office or other area where personal computers and workstations are located, ThinWire Ethernet or unshielded twisted-pair cabling is usually used.
Individual systems can either be connected directly to an Ethernet or gain access to an Ethernet by means of a local area interconnect device, such as a DELNI. A DELNI serves as a concentrator, grouping systems together. Many similar devices, such as hubs and repeaters for the various kinds of cable, also provide the connectivity.
As implemented by Digital, FDDI uses a dual ring of trees topology. It uses one ring as the primary ring, the other ring as a backup, and the tree configuration for increased flexibility, manageability, and availability.
FDDI controllers use a fiber-optic or twisted-pair cable to provide direct access from the processor to the FDDI Token Ring. Note that FDDI networks and Ethernet networks can be combined to form a single extended LAN. This lets applications running on a system connected to FDDI communicate with applications that run on a system connected to Ethernet.
An FDDI concentrator provides for the attachment of FDDI devices such as VAX and Alpha nodes or FDDI-Ethernet bridges to the FDDI LAN.
On Alpha systems, Token Ring controllers use either shielded or unshielded twisted pairs of wire to access the ring. Note that it is difficult to connect a Token Ring LAN directly bridged to any other type of LAN. However, routing protocols to other LANs work easily.
On Alpha systems, LANs over ATM consists of a fiber-optic network based on cell switching. Digital's ATM network uses AAL5 connection-oriented servers for data transmission. For LAN emulation over ATM, Digital implements only the LAN emulation client (LEC) and does not implement the LAN emulation server (LES). The LAN emulation server must be provided by some other facility like the Digital GIGAswitch/ATM. Digital supports one LAN emulation client per ATM adapter.
On Alpha systems, Classical IP (CLIP) implements a new data-link level device that has the same semantics as an Ethernet interface (802.3). This interface is used by a TCP/IP protocol to transmit 802.3 (IEEE Ethernet) frames over an ATM network. The model that OpenVMS Alpha Version 7.1 follows for exchanging IP datagrams over ATM is based on RFC1577 (Classical IP over ATM).
Nodes on the LAN are identified by unique addresses. A message can be sent to one, several, or all nodes on the LAN simultaneously, depending on the address used.
Upon application, IEEE assigns a block of addresses to a producer of LAN nodes. Thus, every manufacturer has a unique set of addresses to use. Normally, one address out of the assigned block of physical addresses is permanently associated with each controller (usually in read-only memory). This address is known as the hardware address of the controller. Each controller has a unique hardware address.
A LAN address is 48 bits in length. LAN addresses are represented as six pairs of hexadecimal digits (six bytes) separated by hyphens (for example, AA-01-23-45-67-FF). The bytes are displayed from left to right in the order in which they are transmitted; bits within each byte are transmitted from right to left. In this example, byte AA is transmitted first; byte FF is transmitted last.
A LAN address can be a physical address of a single node or a multicast address, depending on the value of the low-order bit of the first byte of the address (this bit is transmitted first). The two types of node addresses are:
The local area network (LAN) software includes two system management tools that work in conjunction with the OpenVMS LAN driver system software:
The LAN system management tools:
Table 22-2 describes the LAN management software and the functionality supported on systems running OpenVMS Alpha and OpenVMS VAX.
| Utility | Description | OpenVMS Support | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| LAN Auxiliary Control Program (LANACP) | Runs as a server process whose primary function is to provide MOP downline load service. Other services include maintenance of a LAN volatile device database and a LAN volatile node database. | The LANACP utility provides identical functionality on VAX and Alpha systems running OpenVMS Version 7.0 and later. | |||||||||||||||
| LAN Control Program (LANCP) |
Allows you to control LAN software parameters and obtain information
from the LAN software. You can use the LANCP utility to:
|
OpenVMS Alpha Version 6.1 contained the initial implementation of
LANCP, which did not include MOP-related functions.
OpenVMS Version 6.2 (VAX and Alpha) added MOP-related functions and extended some of this capability to VAX systems. The following table shows how the LAN utility functions are currently supported on VAX and Alpha systems:
|
You can run the LANACP LAN server process to provide the following services:
The LANCP utility allows you to issue instructions to the LANACP process.
Three principal files are connected with LANACP:
In addition, four system logical names, described in Table 22-3, are associated with the LANACP LAN server process.
| Component | Description |
|---|---|
| LAN$DLL | Defines the location of downline load files, where the location of the file is not provided in the load request or explicitly defined in the LAN volatile node database. By default, this is defined as SYS$SYSROOT:[MOM$SYSTEM]. |
| LAN$NODE_DATABASE | Defines the location of the LAN permanent node database. By default, this is defined as SYS$COMMON:[SYSEXE]LAN$NODE_DATABASE.DAT. |
| LAN$DEVICE_DATABASE | Defines the location of the LAN permanent device database. By default, this is defined as SYS$SPECIFIC:[SYSEXE]LAN$DEVICE_DATABASE.DAT. |
| LAN$ACP | Defines the location of the LANACP LAN server process log file, containing entries describing changes to the LAN permanent device and node databases, and load request and load status information. By default, this is defined as SYS$MANAGER:LAN$ACP.LOG. |
To start the LANACP LAN server process, type @SYS$STARTUP:LAN$STARTUP at the DCL prompt or include this line in the SYS$MANAGER:SYSTARTUP_VMS.COM command file to start LANACP automatically at system startup.
The following shows the command line as it appears in SYS$MANAGER:SYSTARTUP_VMS.COM:
$! $! To start the LANACP LAN server application, remove the comment delimiter $! from the command line below. $! $! @SYS$STARTUP:LAN$STARTUP $!
To stop the LANACP LAN server process, enter the SET ACP/STOP command at the LANCP utility prompt.
The LANCP utility allows you to set and show LAN parameters. Section 22.4.1 describes how to invoke the LANCP utility. Table 22-4 describes LAN functions and provides section references to the LANCP commands that help you perform these functions.
| Task | Section |
|---|---|
| Managing LAN devices | Section 22.5 |
| Managing LAN device databases | Section 22.6 |
| Managing LAN node databases | Section 22.7 |
| Managing the MOP downline load service | Section 22.9 |
| Initiating a MOP console carrier connection | Section 22.9.8 |
| Sending MOP trigger boot requests | Section 22.9.9 |
Table 22-5 describes the ways you can invoke and run the LANCP utility (SYS$SYSTEM:LANCP.EXE).
| Command | Example |
|---|---|
| Use the RUN command |
At the DCL command prompt, enter:
$ RUN SYS$SYSTEM:LANCP
The LANCP utility displays the LANCP prompt at which you can enter LANCP commands. |
| 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 command LANCP at the DCL prompt to invoke the utility and enter LANCP commands. When you enter the LANCP command:
|
| Use the MCR command |
At the DCL command prompt, enter:
$ MCR LANCP
When you enter the MCR LANCP command:
|
At the LANCP> prompt, you can enter LANCP commands.
For information about the LANCP utility, enter the HELP command at the LANCP> prompt.
To exit from the LANCP utility, enter the EXIT command or press Ctrl/Z at the LANCP> prompt.
| Command | Function |
|---|---|
| @ (Execute Procedure) | Executes a command procedure. |
| CLEAR DLL++ | Same as the CLEAR MOPDLL command. Clears MOP downline load counters for all nodes and devices. |
| CLEAR DEVICE | Deletes a device from the LAN volatile device database. |
| CLEAR DLL++ | Same as the CLEAR MOPDLL command. Clears MOP downline load counters for all nodes and devices. |
| CLEAR MOPDLL | Clears MOP downline load counters for all nodes and devices. |
| CLEAR NODE | Deletes a node from the LAN volatile node database. |
| CONNECT NODE | Connects to a LAN device, such as a terminal server, that implements a management interface using the MOP console carrier protocol. |
| CONVERT DEVICE_DATABASE | Converts an OpenVMS Version 6.2 format device database to an OpenVMS Version 7.1 format device database. |
| CONVERT NODE_DATABASE | Converts an OpenVMS Version 6.2 format node database to an OpenVMS Version 7.1 format node database. |
| DEFINE DEVICE | Enters a device into the LAN permanent device database or modifies an existing entry. |
| DEFINE NODE | Enters a node into the LAN permanent node database or modifies an existing entry. |
| EXIT | Stops execution of LANCP and returns control to the DCL command level. |
| HELP | Provides online help information about the LANCP utility. |
| LIST DEVICE | Displays information in the LAN permanent device database. |
| LIST NODE | Displays information in the LAN permanent node database. |
| PURGE DEVICE | Deletes a device from the LAN permanent device database. |
| PURGE NODE | Deletes a node from the LAN permanent node database. |
| SET ACP | Modifies the operation of the LANACP LAN server process. |
| SET DEVICE (parameters)++ | Modifies device parameters. |
| SET DEVICE (volatile device database) | Enters a device into the LAN volatile device database or modifies an existing entry. |
| SET NODE | Enters a node into the LAN volatile node database or modifies an existing entry. |
| SHOW CONFIGURATION | Displays a list of LAN devices on the system. |
| SHOW DEVICE | Displays information in the LAN volatile device database. |
| SHOW DLL++ | Displays the current state of MOP downline load services. |
| SHOW LOG | Displays recent downline load activity. |
| SHOW MOPDLL | Displays the current state of MOP downline load services. |
| SHOW NODE | Displays information in the LAN volatile node database. |
| SPAWN | Creates a subprocess of the current process. |
| TRIGGER NODE | Issues a request to reboot to a remote node. |
| UPDATE DEVICE++ | Updates firmware image for a device. |
For detailed information about LANCP commands and qualifiers, see the OpenVMS System Management Utilities Reference Manual: A--L.
Use the SPAWN command to create a subprocess of the current process. The SPAWN command copies the context of the subprocess from the current process. This allows you to exit temporarily from LANCP without having to restart LANCP when you resume.
The syntax for the SPAWN command is as follows:
SPAWN [command-string]
You can set up the LANCP utility to execute commands from a command file from within LANCP. The LANCP utility recognizes the command file as the file name preceded by the at sign (@). The default file name extension is .COM.
LAN device management consists of displaying device characteristics and setting device parameters. You can use the LANCP utility to set parameters for the types of LAN devices shown in Table 22-7.
| LAN | Device Examples | Description |
|---|---|---|
| Ethernet | DE425, DE434, DE435, DE436, DE500, DECchip 21040 |
Allow the selection of media type (type of cable connected) and the
speed of connection (Ethernet or FastEthernet).
Allow full-duplex operation (point-to-point operation between a similar device or between the device and a switch). |
| FDDI | DEFTA, DEFPA, DEFAA, DEFEA, DEMFA,DEMNA | Allow full-duplex operation. |
| Token Ring++ | DETRA, DW300, DW110 | Allow the setting of Token Ring parameters and the definition of source routing and functional address mapping. |
| All | Any | Allow the setting of generic parameters such as the number of receive buffers. |
| ATM++ | ATMworks 350, ATMworks 750 | The ATMworks 350 supports PCI-based systems. The ATMworks 750 supports TURBOchannel systems. |
To display the LAN devices on the system, enter the SHOW CONFIGURATION command using the following syntax:
SHOW CONFIGURATION
Example
LANCP> SHOW CONFIGURATION
LAN Configuration:
Device Medium Default LAN Address Version
------ ------ ------------------- -------
EWA0 CSMA/CD 08-00-2B-E4-00-BF 02000023
EWB0 CSMA/CD 08-00-2B-92-A4-0D 02000023
IRA0 Token Ring 00-00-93-58-5D-32 20000223
This command displays the output from a SHOW CONFIGURATION command that was entered on a node that has three LAN devices: two DE435s, and a DETRA:
The version is the device-specific representation of the actual version. In this example, for two devices on the PCI bus, the actual version is in the low byte (2.3 for the DE435 adapters). A device that does not have a readable version is shown as version zero.
6017P066.HTM OSSG Documentation 22-NOV-1996 14:22:53.97
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.