LANCP, or the LAN Control Program, is the utility that allows you to configure and control the LAN software and hardware on OpenVMS systems. It is part of OpenVMS and invoked by running SYS$SYSTEM:LANCP.EXE (via either RUN or MCR).
LANCP can be used to:
- set LAN parameters to customize the LAN environment
- display LAN settings and counters
- provide MOP downline load support for devices such as terminal servers, x-terminals, and LAN printers, and for booting satellites in an OpenVMS Cluster environment
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 the table below:
|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 (Alpha only)||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 (Alpha only)||ATMworks 350, ATMworks 750||The ATMworks 350 supports PCI-based systems. The ATMworks 750 supports TURBOchannel systems|
The LAN volatile and permanent device databases contain a single entry for each LAN device that exists on the system. Each entry in the LAN volatile device database contains device information and MOP downline load counters information. Each entry in the LAN permanent device database contains device information that is used to populate the volatile database when the LANACP LAN server process is started.
Typically, each database contains the same devices. However, the permanent database may contain entries for devices that have not yet been configured or installed in the system. The LANACP LAN server process maintains the volatile device database. The LANCP utility maintains the permanent device database. You can manipulate either database using the LANCP utility commands depending on your user privileges. Privileged users can add or delete device entries from each database, enable or disable MOP downline load service, and clear MOP downline load counters information for LAN devices. Unprivileged users can view the MOP downline load status and counters information.
Commands to view and modify the LAN device databases include:
|Action||Permanent database||Volatile database|
|View||LIST DEVICE||SHOW DEVICE|
|Modify||DEFINE DEVICE||SET DEVICE|
|@||Execute a command procedure containing LANCP commands. The default file extension is .COM.||
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 <...>
|CLEAR DDL (Alpha only)||Same as the CLEAR MOPDLL command. Clears MOP downline load counters for all nodes and devices.||
LANCP> CLEAR DLL This command clears MOP downline load counters from the LAN volatile device and node databases for all nodes and devices.
|CLEAR DEVICE||Deletes a device from the LAN volatile device database.||
LANCP> CLEAR DEVICE EXA0
This command deletes device EXA0 from the LAN volatile device database
|CLEAR MOPDLL||Clears MOP downline load counters for all nodes and devices.|
|CLEAR NODE||Deletes a node from the LAN volatile node database.||
LANCP> CLEAR NODE VAXSYS <nowiki> This command deletes the node VAXSYS 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. | <nowiki> 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.
LANCP> CONNECT NODE TERM_SERVER/DEVICE=EWA0/INPUT=LOGOUT_PORT_3.COM
This command attempts a console-carrier connection to node TERM_SERVER to send the contents of the command file LOGOUT_PORT_3.COM.
|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. (To access the volatile device database, use SET DEVICE; see LANCP Permanent Device Database for qualifiers that can be used with the DEFINE DEVICE command).||
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 <nowiki> This command sets all LAN devices defined in the LAN permanent device database to nonexclusive mode for LANACP MOP downline load service. <nowiki> 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.
|DEFINE NODE||Enters a node into the LAN permanent node database or modifies an existing entry.||
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.
|EXIT||Stops execution of LANCP and returns control to the DCL command level.||
LANCP> exit $
|HELP||Provides online help information about the LANCP utility.||
LANCP> help Information available: @ CLEAR Commands CONNECT CONVERT DEFINE EXIT HELP LIST PURGE SET SHOW SPAWN TRIGGER UPDATE Usage_Summary Topic?
|LIST DEVICE||Displays information in the LAN permanent device database. (To display devices in the volatile device database, use the SHOW DEVICE command. Also see LANCP Permanent Device Database for qualifiers that can be used with the LIST DEVICE command).||
LANCP> LIST DEVICE/MOPDLL Device Listing, permanent database: --- MOP Downline Load Service Characteristics --- Device State Access Mode Clients Data Size ------ ----- ----------- ------- --------- EXA0 Enabled Exclusive KnownClientsOnly 1400 bytes FXA0 Disabled NoExclusive NoKnownClientsOnly 246 bytes
|LIST NODE||Displays information in the LAN permanent node database.||
LANCP> LIST NODE 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
|PURGE DEVICE||Deletes a device from the LAN permanent device database.||
LANCP> PURGE DEVICE/ALL
This command deletes all devices from the LAN permanent device database.
|PURGE NODE||Deletes a node from the LAN permanent node database.||
LANCP> PURGE NODE/ALL
This command deletes all nodes from the LAN permanent node database.
|SET ACP||Modifies the operation of the LANACP LAN server process.||
LANCP> SET ACP/ECHO/FULL
This command enables tracing of received and transmitted downline load messages. The /FULL qualifier displays the entire contents of received and transmitted downline load messages.
|SET DEVICE (volatile device database)||Enters a device into the LAN volatile device database or modifies an existing entry. For accessing the LAN permanent device database, use DEFINE DEVICE. See LANCP Volatile Device Database for the qualifiers to SET DEVICE.|
|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.||
LANCP> show config SMAN43 LAN Configuration (13-MAR-2019 08:51:29.73): Parent or Device PrefCPU Medium/User Version Link Speed Duplex Auto BufSize MAC Address Type Description ------ ------- ----------- ------- ---- ----- ------ ---- ------- ---------------- ------------ ----------- EWA0 0 Ethernet (nopriv) Up 1000 Full Yes 1500 00-22-64-94-BC-6F UTP BCM5704 EWB0 1 Ethernet (nopriv) Up 1000 Full Yes 1500 00-22-64-94-BC-6E UTP BCM5704
|SHOW DEVICE||Displays information in the LAN volatile device database. If no qualifiers are specified, the utility displays all matching devices without additional information. See LANCP Volatile Device Database for qualifiers that can be used with the SHOW DEVICE command.||
LANCP> show dev ewa0 SMAN43 Device Listing, volatile database (13-MAR-2019 09:03:18.11): Device ------ EWA0
|SHOW DLL (Alpha only)||Displays the current state of MOP downline load services.|
|SHOW LOG||Displays recent downline load activity.||
LANCP> show log SMAN43 SYS$MANAGER:LAN$ACP.LOG latest contents (13-MAR-2019 09:36:46.97): 6-MAR-2019 14:10:29.35 Defined LAN$DLL to be SYS$SYSROOT:[MOM$SYSTEM] 6-MAR-2019 14:10:29.43 Found LAN device EWA0, hardware address 00-22-64-94-BC-6F 6-MAR-2019 14:10:29.45 Found LAN device EWB0, hardware address 00-22-64-94-BC-6E 6-MAR-2019 14:10:29.49 %EWA0, Auto-negotiation mode assumed set by console 6-MAR-2019 14:10:29.49 %EWA0, Merl5704 located in 64-bit, 66-mhz PCI-X slot 6-MAR-2019 14:10:29.50 %EWA0, Device type is BCM5704C (UTP) Rev B0 (21000000) 6-MAR-2019 14:10:29.50 %EWB0, Auto-negotiation mode assumed set by console 6-MAR-2019 14:10:29.51 %EWB0, Merl5704 located in 64-bit, 66-mhz PCI-X slot 6-MAR-2019 14:10:29.53 %EWB0, Device type is BCM5704C (UTP) Rev B0 (21000000) 6-MAR-2019 14:10:29.54 %EWA0, Link up: 1000 mbit, full duplex, flow control (txrx) 6-MAR-2019 14:10:29.54 %EWB0, Link up: 1000 mbit, full duplex, flow control (txrx) 6-MAR-2019 14:10:29.55 Node database file, LAN$NODE_DATABASE, not found 6-MAR-2019 14:10:29.65 LANACP initialization complete
|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 (Alpha only)||Updates firmware image for a device.|