Previous | Contents | Index |
Converts the device database to the format required by LANCP. If the database is not updated, LANCP can read the database but does not convert an entry in it unless the entry is changed. The conversion is necessary when the contents of the device entry change from one OpenVMS release to the next. Usually, LANCP and LANACP automatically update entries as required.Requires SYSPRV privilege.
CONVERT DEVICE_DATABASE device_database
None.
None.
Converts the node database to the format required by LANCP. If the database is not updated, LANCP can read the database but does not convert an entry in it unless the entry is changed. The conversion is necessary when the contents of the node entry changes from one OpenVMS release to the next. Usually, LANCP and LANACP automatically update entries as required.Requires SYSPRV privilege.
CONVERT NODE_DATABASE node_database
None.
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.
DEFINE DEVICE device-name
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.
#1 |
---|
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.
#2 |
---|
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.
#3 |
---|
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.
DEFINE NODE node-name
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.
#1 |
---|
LANCP> DEFINE NODE GALAXY/ADDRESS=08-00-2B-11-22-33 - /FILE=APB.EXE - /ROOT=$64$DIA14:<SYS10.> - /BOOT_TYPE=ALPHA_SATELLITE |
This command sets up node GALAXY 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.
#2 |
---|
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.
Stops execution of LANCP and returns control to the DCL command level. You can also enter Ctrl/Z at any time to exit.
EXIT
None.
None.
LANCP> EXIT $ |
This command stops execution of LANCP and returns control to the DCL command level.
Provides online help information about the LANCP utility.
HELP [topic]
topic
Specifies a subject for which you want information---a LANCP command or LANCP command and command keyword. If you enter the HELP command with a command name only, such as HELP SET, LANCP displays a list of all of the command keywords used with the SET command.
None.
LANCP> HELP DEFINE DEVICE DEFINE DEVICE DEVICE device-name/qualifiers DEVICE/ALL/qualifiers Sets device specific parameters for the specified LAN devices. Requires SYSPRV privilege. Additional information available: Parameters Qualifiers /ALL /ATMADDRESS /DLL /ELAN /MOPDLL /VOLATILE_DATABASE /UPDATE Examples DEFINE DEVICE Subtopic? |
This command provides online help for the LANCP command DEFINE DEVICE.
Displays information in the LAN permanent device database.
LIST DEVICE device-name
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 DE435 Ethernet device is specified as EWA0, the second as EWB0.For example, you can specify a DEMNA controller as EXA, EXA0, or EXA0:. This refers to the LAN template device, for which is maintained most of the device parameters and counters. Also, the device name can refer to a device unit representing an actual user or protocol. For example, the cluster protocol can be started on a device as EWA1. You can specify a device unit to view unit-specific parameter information.
If you do not specify a device name, all devices are displayed.
If you specify a device name, all matching LAN devices are displayed, for example: E to select all Ethernet devices, F for FDDI, I for Token Ring, EW to select all Ethernet PCI Tulip devices.
If you do not specify a qualifier, the utility displays the matching devices without additional information. |
/ALL
Lists all devices in the LAN permanent device database./CHARACTERISTICS or /PARAMETERS
Lists status and related information about the device./DLL or /MOPDLL
Displays MOP downline load characteristics./MAP
Lists the current configuration of the functional address mapping table for a Token Ring device./OUTPUT=file name
Creates the specified file and directs output to it./SR_ENTRY
Lists the contents of the current source routing cache table./TRACE
Lists driver trace parameters set for the device.
#1 |
---|
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 |
This command displays MOP downline load information in the LAN permanent device database for all known devices.
Displays information in the LAN permanent node database, especially MOP downline load information.
LIST NODE node-name
node-name
Specifies the node name. The name can include up to 63 characters associated with the node address. If no node name is given, all nodes are displayed.
/ALL
Displays data for all nodes in the LAN permanent node database. If you specify a node name, all matching nodes are selected; for example, A/ALL selects all nodes beginning with A./OUTPUT=file-name
Creates the specified file and directs output to that file. If the file extension is .com, 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.
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 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 |
This example shows output from a LIST NODE command issued on a local node on which there are three nodes defined (GALAXY 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.
Deletes device data from the LAN permanent device database. Requires SYSPRV privilege.
PURGE DEVICE device-name
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 DE435 Ethernet device is specified as EWA0, the second as EWB0.For example, you can specify a DEMNA controller as EXA, EXA0, or EXA0:. To select all LAN devices, omit the device name and include the /ALL qualifier.
/ALL
Deletes data for all LAN devices in the LAN permanent 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 Ethernet PCI Tulip 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.
LANCP> PURGE DEVICE/ALL |
This command deletes all devices from the LAN permanent device database.
Deletes a node from the LAN permanent node database. Requires SYSPRV privilege.
PURGE NODE node-name
node-name
Supplies the name of a node in the LAN permanent node database.
/ALL
Deletes all LAN nodes in the LAN permanent 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.
LANCP> PURGE NODE/ALL |
This command deletes all nodes from the LAN permanent node database.
Modifies the operation of the LANACP LAN Server process. Requires SYSPRV privilege.
SET ACP
None.
/ECHO
/NOECHO (default)
Enables partial tracing of received and transmitted downline load messages (the first 32 bytes of the data portion of each message). Note that the last one or two MOP messages are displayed in full: the memory load message with cluster parameters, and the parameter load with transfer address message, where present in the load.The data is written to a log file SYS$MANAGER:LAN$node-name.LOG.
To obtain the entire contents of each message, use the /FULL qualifier as follows:
SET ACP/ECHO/FULL
/FULL
/NOFULL (default)
When /ECHO is enabled, displays the entire contents of received and transmitted downline load messages./OPCOM (default)
/NOOPCOM
Enables OPCOM messages from LANACP LAN Server process.Messages are generated by the LANACP LAN Server process when a 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.
/STOP
Stops the LANACP process. It can be restarted by reexecuting the SYS$STARTUP:LAN$STARTUP command file.
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.
Sets or modifies LAN device parameters. Requires PHY_IO privilege.
SET DEVICE device-name
device-name
Specifies a device to be entered in the LAN volatile device database, or whose parameters are 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 DE435 Ethernet device is specified as EWA0, the second as EWB0.
/ALL
Sets data for all LAN devices. 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 Ethernet PCI Tulip devices./DEVICE_SPECIFIC=(FUNCTION="xxxx",VALUE=(n1,n2,n3...n16))
/NODEVICE_SPECIFIC
Allows some device-specific parameters to be adjusted. These are useful for debug purposes or for experiments while doing performance measurements. Like other LANCP commands which affect devices, this command requires SYSPRV privilege.Specify the negated qualifer to clear all device-specific parameter data.
These functions are described in a text file on the system, SYS$HELP:LAN_COUNTERS_AND_FUNCTIONS.TXT.
/DLL or MOPDLL=(enable-option, exclusive-option, size-option, knownclientsonly-option)
Provides the MOP downline load service settings for the device.Note that defaults apply to creation of an entry in the device database. If an existing entry is being modified, fields not specified remain unchanged.
You can specify the following keywords with this qualifier:
- enable-option
ENABLE
DISABLE (default)
Specify ENABLE or DISABLE to indicate that MOP downline load service should be enabled or disabled for the device.- exclusive-option
EXCLUSIVE
NOEXCLUSIVE (default)
Specify EXCLUSIVE to indicate that no other provider of MOP downline load service is allowed on the specified LAN device at the same time as LANACP. Specify NOEXCLUSIVE to indicate that the LAN MOP downline load service can coexist with other implementations (in particular, the DECnet Phase IV and DECnet Plus implementations that include MOP support).
Note that when you select NOEXCLUSIVE, LANACP responds only to MOP downline load requests directed to nodes defined in the LAN node database.- size-option
SIZE=value
Use SIZE=value to specify the size in bytes of the file data portion of each downline load message. The permitted range is 246 to 1482 bytes. The default value is 246 bytes, which should allow any client to load properly. Note that some clients may not support the larger size.
The recommended size for better load performance and less server overhead is the largest size that results in successful loads of all clients. The 1482 value is derived from the maximum packet size for CSMA/CD (Ethernet) of 1518 bytes less the 802e header and CRC (26 bytes) and MOP protocol overhead (10 bytes).
You can override the size on a per-node basis. See the SET NODE commands for details.- knownclientsonly-option
KNOWNCLIENTSONLY
NOKNOWNCLIENTSONLY (default)
Specify KNOWNCLIENTSONLY to indicate that MOP downline load requests should be serviced only for clients defined in the LAN permanent node database. When you select NOKNOWNCLIENTSONLY, LANACP searches the LAN$DLL directory for any images requested by clients that are not defined in the LAN node database.
Note that this option is not available when NOEXCLUSIVE mode has been selected. When NOEXCLUSIVE mode is selected, LANACP services MOP downline load requests only for clients defined in the LAN node database./MAX_BUFFERS=value
Sets the maximum number of receive buffers to be allocated and used by the LAN driver for the LAN device./MIN_BUFFERS=value
Sets the minimum number of receive buffers to be allocated and used by the LAN driver for the LAN device./PERMANENT (SET DEVICE only)
Updates the device entries in the LAN volatile device database with any data currently set in the permanent database. This allows you to update the volatile database after changing data in the permanent database, rather than repeating the commands for each updated entry to apply the changes to the volatile database./TAG=value
Specifies the IEEE 802.1Q tag for the VLAN device.
value is the IEEE 802.IQ tag number./TRACE=size-option, mask-option, stop-option
/NOTRACE
Provides the LAN driver trace settings for the device. By default, most LAN drivers do tracing of error conditions and state changes. Tracing is controlled by an event mask that selects the events to trace, a stop mask that specifies when to stop tracing, and the size of the trace buffer.You can change tracing settings at any time. The LAN driver allocates the trace buffer from non-paged pool. You can calculate the amount of pool needed by multiplying the number of entries by the size of each entry, 32-bytes.
The impact of tracing on the system is negligible for error and state change events, more significant when all events are selected, and very significant when full packet tracing is enabled.
The command SHOW DEVICE/TRACE displays trace results as well as the trace mask.
You can specify the following keywords with this qualifier:
- size-option
SIZE=value
Use SIZE=value to specify the size of the trace buffer in entries, each 32 bytes. The default is 2048 entries. The permitted range is 256 to 1000000.
The size MOD 3 encodes the amount of packet data to include, either 35 bytes, 66 bytes, 97 bytes, or the entire packet.- mask-option
MASK=(value1,value2)
Use MASK=(value1,value2) to specify the trace mask to select which type of entries should be collected in the trace buffer. The first 32 bits consist of events common to most LAN drivers. The second 32 bits consist of events specific to the LAN driver for the specified device.- stop-option
STOP=(value1,value2)
Use STOP=(value1,value2) to specify the trace mask to select which type of entries should stop tracing. When a trace entry is made that matches one of the bits in the stop mask, the trace mask is cleared so that you can look at the trace data accumulated so far./UPDATE (DEFINE DEVICE only)
Adds LAN devices that are not currently in the LAN permanent device database to that database. The initial entry for the device uses default values for all parameters. To update the permanent database with current information from the volatile database, use the DEFINE DEVICE command with the /VOLATILE qualifier. You can combine the /UPDATE and /VOLATILE qualifiers in a single DEFINE DEVICE command./UPDATE (SET DEVICE only)
Adds LAN devices that are not currently in the LAN volatile device database to that database. The initial entry for the device uses default values for all parameters. To update the volatile database with current information from the permanent database, use the SET DEVICE command with the /PERMANENT qualifier. You can combine the /UPDATE and /PERMANENT qualifiers in a single SET DEVICE command./VLAN_DEVICE=device-name
/NOVLAN_DEVICE
Specifies the physical LAN device that is to host the VLAN device. The /NOVLAN_DEVICE qualifier requests deactivation of the VLAN device.When deactivating the VLAN device, the device-name is not required because the VLAN driver knows which device is hosting the VLAN device.
Note that a VLAN device cannot be deactivated if any applications continue to use the device.
/VOLATILE (DEFINE DEVICE only)
Updates the device entries in the LAN permanent device database with any data currently set in the volatile database. This allows you to update the permanent database after changing data in the volatile database, rather than repeating the commands for each updated entry to apply the changes to the permanent database.
/AUTONEGOTIATE (default)
/NOAUTONEGOTIATE
Enables or disables the use of auto-negotiation to determine the link settings. You may need to disable link auto-negotiation when connected to a switch or device that does support auto negotiation./FLOW_CONTROL (default)
/NOFLOW_CONTROL
Enables flow control on a LAN device./FULL_DUPLEX
/NOFULL_DUPLEX (default)
Enables full-duplex operation of a LAN device. Before full-duplex operation results from the use of this qualifier, additional device or network hardware setup may be required. Some devices may be enabled for full-duplex operation by default. Some devices may not allow the setting to be changed.
Previous Next Contents Index