HP OpenVMS Systems Documentation |
HP OpenVMS System Management Utilities Reference Manual
Valid values are either 4 or 16, indicating 4 megabits per second or 16 megabits per second. The default value for Token Ring is 16, unless the LAN adapter supports a nonvolatile mechanism for setting this parameter. /SR_ENTRY=(LAN_ADDRESS=address, RI=routing-information)/NOSR_ENTRY=(LAN_ADDRESS=address)Statically defines a specific source-routed route for a specific node. The default value is no routes specified. This caching remains valid while used or until the aging timer expires.Use this qualifier only as a last resort when isolating communication failures on extended LAN topologies. The /NOSR_ENTRY=(LAN_ADDRESS=address) qualifier, clears the previously defined static source routed route. The address is a standard 6-byte LAN address (given as hexadecimal byte characters separated by hyphens), which specifies the canonical form of the address. Using a colon as the separator character indicates the bit-reversed form of the address. The routing-information is the source routing field, specified as a series of two-byte hexadecimal characters (each byte separated by a hyphen). The field consists of a two-byte routing control field followed by up to 14 two-byte segment identifiers, each containing the ring number and the bridge number used in the hop. Qualifiers (ATM Devices)
Examples
SET NODE
Enters a node into the LAN volatile node database or modifies an existing entry. Requires SYSPRV privilege. FormatSET NODE node-name Parameter
Qualifiers
|
| #1 |
|---|
LANCP> SET NODE VAXSYS/ADDRESS=08-00-2B-11-22-33 -
/FILE=APB.EXE -
/ROOT=$64$DIA14:<SYS10.> -
/BOOT_TYPE=ALPHA_SATELLITE
|
This command sets up node VAXSYS for booting as an Alpha satellite into the 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> SET NODE VAXSYS/ADDRESS=08-00-2B-11-22-33 -
/FILE=NISCS_LOAD.EXE -
/ROOT=$64$DIA14:<SYS10.> -
/BOOT_TYPE=VAX_SATELLITE
|
This command sets up node VAXSYS for booting as a VAX satellite into the 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.
| #3 |
|---|
LANCP> SET NODE VAXSYS/ADDRESS=08-00-2B-11-22-33/NOROOT
|
This command changes the LAN address associated with node VAXSYS and clears the current root specification.
| #4 |
|---|
SET 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 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.
Displays the current settings for LANCP and LANACP.
SHOW ACP
None.
/OUTPUT=file-name
Creates the specified file and directs output to it.
LANCP> SHOW ACP
LANCP/LANACP options:
Verify is OFF
OPCOM messages are ENABLED
DLL packet tracing is DISABLED
|
This example shows how LANCP and LANACP are currently configured.
Displays a list of LAN devices and characteristics on the system.
SHOW CONFIGURATION
None.
/OUTPUT=file-name
Creates the specified file and directs output to it./USERS
Shows which protocols are using which template device.
LANCP> SHOW CONFIGURATION/USERS LAN Configuration:
|
This example shows the output from a SHOW CONFIGURATION command that was entered on a node that has eleven LAN devices, one of which is actively in use.
Displays information in the volatile device database. If the LANACP process is not running, displays a list of current LAN devices.
SHOW 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 specific device units 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
Shows all devices that match device name./CHARACTERISTICS or PARAMETERS
Displays status and related information about the device./COUNTERS
Displays device counters./DLL or MOPDLL
Displays LAN volatile device database information related to MOP downline load for the device./INTERNAL_COUNTERS
Displays internal counters. By default, it does not display zero counters. To see all counters, including zero, use the additional qualifier /ZERO. To see the debug counters, use the additional qualifier /DEBUG./MAP
Displays the current configuration of the functional address mapping table./MESSAGES
Displays the console messages displayed by the LAN driver as part of the LAN driver internal counters. This qualifier is included for convenience, to avoid scanning the internal counters to get to the message data./OUTPUT=file-name
Creates the specified file and directs output to it./REVISION
Displays the current LAN driver and device revision information, if available or applicable. Not all LAN drivers maintain revision information./SR_ENTRY
Displays the contents of the current Token Ring source routing cache table./TRACE
Displays LAN driver trace data.
| #1 |
|---|
LANCP> SHOW DEVICE/COUNTERS EXA0
Device Counters EXA0:
Value Counter
----- -------
259225 Seconds since last zeroed
5890496 Data blocks received
4801439 Multicast blocks received
131074 Receive failure
764348985 Bytes received
543019961 Multicast bytes received
3 Data overrun
1533610 Data blocks sent
115568 Multicast packets transmitted
122578 Blocks sent, multiple collisions
86000 Blocks sent, single collision
189039 Blocks sent, initially deferred
198120720 Bytes sent
13232578 Multicast bytes transmitted
7274529 Send failure
0 Collision detect check failure
0 Unrecognized frame destination
0 System buffer unavailable
0 User buffer unavailable
|
This command displays counters for Ethernet device EXA0.
| #2 |
|---|
LANCP> SHOW DEVICE/MAP ICA0
Multicast to Functional Address Mapping ICA0:
Multicast address Functional Address Bit-Reversed
----------------- ------------------ ------------
09-00-2B-00-00-04 03-00-00-00-02-00 C0:00:00:00:40:00
09-00-2B-00-00-05 03-00-00-00-01-00 C0:00:00:00:80:00
CF-00-00-00-00-00 03-00-00-08-00-00 C0:00:00:10:00:00
AB-00-00-01-00-00 03-00-02-00-00-00 C0:00:40:00:00:00
AB-00-00-02-00-00 03-00-04-00-00-00 C0:00:20:00:00:00
AB-00-00-03-00-00 03-00-08-00-00-00 C0:00:10:00:00:00
09-00-2B-02-00-00 03-00-08-00-00-00 C0:00:10:00:00:00
09-00-2B-02-01-0A 03-00-08-00-00-00 C0:00:10:00:00:00
AB-00-00-04-00-00 03-00-10-00-00-00 C0:00:08:00:00:00
09-00-2B-02-01-0B 03-00-10-00-00-00 C0:00:08:00:00:00
09-00-2B-00-00-07 03-00-20-00-00-00 C0:00:04:00:00:00
09-00-2B-00-00-0F 03-00-40-00-00-00 C0:00:02:00:00:00
09-00-2B-02-01-04 03-00-80-00-00-00 C0:00:01:00:00:00
09-00-2B-02-01-07 03-00-00-02-00-00 C0:00:00:40:00:00
09-00-2B-04-00-00 03-00-00-04-00-00 C0:00:00:20:00:00
09-00-2B-02-01-00 03-00-00-00-08-00 C0:00:00:00:10:00
09-00-2B-02-01-01 03-00-00-00-10-00 C0:00:00:00:08:00
09-00-2B-02-01-02 03-00-00-00-20-00 C0:00:00:00:04:00
03-00-00-00-00-01 03-00-00-00-00-01 C0:00:00:00:00:80
03-00-02-00-00-00 03-00-02-00-00-00 C0:00:40:00:00:00
|
This command displays mapping information for Token Ring device ICA0.
| #3 |
|---|
LANCP> SHOW DEVICE/MOPDLL
Device Listing, volatile 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 volatile device database for all known devices.
| #4 |
|---|
LANCP> SHOW DEVICE/MOPDLL EXA0
Device Listing, volatile database:
--- MOP Downline Load Service Characteristics ---
Device State Access Mode Clients Data Size
------ ----- ----------- ------- ---------
EXA0 Enabled Exclusive KnownClientsOnly 1400 bytes
|
Previous Next Contents Index