 |
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)
/ATMADDRESS=LES
Sets the LAN emulation server (LES) address for asynchronous transfer
mode (ATM). Usually the address is not user specified, and this
qualifier is used only if you want a specific address. By default the
address is determined by software from the configuration server for the
LES.
The /ATMADDRESS=LES qualifier's syntax is as follows:
SET DEVICE/ATMADDRESS = ([NO]LES=the ATM server)
|
/ATMADDRESS=ARP
Sets the address resolution protocol (ARP) server address for Classical
IP over ATM. This qualifier is required before a LIS is enabled if the
local host is not the ARP server.
The /ATMADDRESS=ARP qualifier's syntax is as follows:
SET DEVICE/ATMADDRESS = (ARP=atm_arp_server)
|
/CLIP
Sets the Classical Internet Protocol (CLIP) over ATM (RFC1577). The
CLIP qualifier implements a data-link level device as a client and/or a
server in a logical IP subnet (LIS). This allows the IP protocol to
transmit Ethernet frames over the ATM network. The /CLIP = ENABLE
command causes the system to join the LIS. The /CLIP = DISABLE command
causes the client to leave the logical IP subnet.
Note that a LIS requires a server, and there must be only one server
for each subnet. Communication between subnets can only be performed by
a router. There can only be one client for each ATM adapter.
The /CLIP qualifier's syntax with standard Internet dotted notation is
as follows:
SET DEVICE/CLIP =(ip_subnet=a.b.c.d,
ip_address=a.b.c.d,
parent=devnam,
name="ip subnet name",
enable, disable
type = client|server)
|
The meanings for the syntax for /CLIP are as follows:
| Option |
Meaning |
|
ip_address
|
Specifies the IP address of the CLIP client.
|
|
ip_subnet
|
Specifies the subnet mask of the CLIP client.
|
|
parent=devnam
|
Specifies the parent device name.
|
|
name
|
Specifies a name for the LIS to aid in operations and diagnostics.
|
|
type=client
|
Starts up a classical IP client only. This is the default.
|
|
type=server
|
Starts up a classical IP server. Only one server for each LIS is
allowed, and the server needs to be started first.
|
|
type=(server,client)
|
Starts up a classical IP server and client.
|
Keywords and their meaning for /CLIP are as follows:
| Keyword |
Meaning |
|
Enable
|
Joins the logical IP subnet.
|
|
Disable
|
Causes a client to leave the logical IP subnet.
|
/ELAN
The /ELAN qualifier has two values: enable and disable. With
/ELAN=ENABLE along with the keyword STARTUP, the LAN emulation is
loaded when LANACP starts. With /ELAN=DISABLE, the same parameters used
with ENABLE can be invoked.
The /ELAN qualifier's syntax is as follows:
DEFINE DEVICE/ELAN =(parent=parent device,
name="ELAN NAME to join",
size=1516
type=CSMACD
Enable,
Disable,
description = "description string,")
|
The meaning of the syntax for /ELAN is as follows:
| Option |
Meaning |
|
parent
|
The ATM adapter device name. An example of the parent device for DAPCA
is: HW
n0, where
n is the controller number. An example of the parent device
for DGLTA is: HC
n0, where
n is the controller number.
|
|
name
|
Optionally specified if you want to join a specific ELAN. The default
is null.
|
|
size
|
Maximum frame size of the LAN you want to join. Valid sizes are 1516,
4544, or 9234 bytes. The default is 1516.
|
|
type
|
Support currently only for CSMACD, which is the default.
|
|
description
|
A method of describing the ELAN for display purposes only.
|
Keywords and their meanings for /ELAN are as follows:
| Keyword |
Meaning |
|
Enable
|
Begins a join on a specified emulated LAN. It also loads the driver, if
not already loaded.
|
|
Disable
|
Causes a client to leave the emulated LAN.
|
/PVC=(vci[,...])
/[NO]PVC=(vci[,...])
Sets the permanent virtual circuit (PVC) to be used by a Classical IP
over ATM client. This is an optional qualifier.
A list of PVCs is defined for use by CLIP clients. This command should
be used before enabling the CLIP client. The PVC has to be set up
manually in the ATM switch.
The vci is the VCI (Virtual Circuit ID) of the PVC to
be used.
Examples
|
1. LANCP> SET DEVICE/CONTENDER/MEDIA=UTP/NOEARLY/SOURCE ICA0
|
Enables monitor contention, UTP cable media, source routing and
disables early token release for Token Ring device ICA0.
|
2. LANCP> SET DEVICE/MEDIA=TWI EWB0
|
Sets the media type to twisted pair for the second Tulip Ethernet
device, EWB0.
|
3. LANCP> SET DEVICE EXA0/MOPDLL=ENABLE
|
Enables MOP downline load service for device EXA0, leaving the
remaining MOPDLL parameters unchanged.
|
4. LANCP> SET DEVICE EXA0/MOPDLL=(ENABLE,EXCLUSIVE,SIZE=1482)
|
Enables MOP downline load service for device EXA0, in exclusive mode
with the data transfer size of 1482 bytes, leaving the remaining MOPDLL
parameters unchanged.
|
5. LANCP> SET DEVICE EXA0/MOPDLL=(ENABLE,NOEXCLUSIVE)
LANCP> SET DEVICE FXA0/MOPDLL=(ENABLE,EXCL,KNOWN)
|
These commands enable LANACP MOP downline load service for:
- LAN device EXA0 in nonexclusive mode
- LAN device FXB0 in exclusive mode for only known clients
SET NODE
Enters a node into the LAN volatile node database or modifies an
existing entry. Requires SYSPRV privilege.
Format
SET NODE node-name
Parameter
node-name
Supplies the name of a node to be added to the LAN volatile 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.
Qualifiers
/ADDRESS=node-address
/NOADDRESS (default)
Associates a LAN address with the node name. Specify the address as 6
bytes in hexadecimal notation, separated by hyphens. The address does
not have to be unique (as might be the case when the address is not
known, so a nonexistent address is specified).
If multiple node addresses are to be associated with a node name, each
combination may be given as a node name with an extension, for example,
VAXSYS.EXA for the EXA device on node VAXSYS, or VAXSYS_1 for the first
LAN device on node VAXSYS.
If you do not specify the /ADDRESS qualifier, the setting remains
unchanged. The /NOADDRESS qualifier clears the field.
/ALL
Defines data for all nodes in the LAN volatile node database. If you
specify a node name, all matching nodes are selected; for example,
A/ALL selects all nodes beginning with A.
/BOOT_TYPE=boot-option
/NOBOOT_TYPE
Indicates the type of processing required for downline load requests.
You can specify one of the following keywords with this qualifier:
- VAX_SATELLITE---a VAX satellite cluster boot
- ALPHA_SATELLITE---an Alpha satellite cluster boot
- I64_SATELLITE---an OpenVMS Cluster I64 satellite boot
- OTHER---the specified image; noncluster satellite loads that do not
require additional data
The distinction is necessary, because OpenVMS Cluster satellite loads
require additional cluster-related data be appended to the load image
given by the /FILE qualifier. The default value is OTHER.
If you do not specify the /BOOT_TYPE qualifier, the setting remains
unchanged. The /NOBOOT_TYPE qualifier clears the field.
Note that I64 satellites boot using TFTP rather than MOP services. This
boot type is included so that the information in the node database can
be maintained, not because it is needed for booting purposes.
/DECNET_ADDRESS=value
/NODECNET_ADDRESS
Associates a DECnet address with the node name. Specify the address in
DECnet notation, xx.xxxx.
If you do not specify the /DECNET_ADDRESS=value qualifier,
then the setting remains unchanged. The /NODECNET_ADDRESS qualifier
clears the field.
/FILE=file-spec
/NOFILE
Supplies the file name of a boot file to be used when the downline load
request does not include a file name (for example, OpenVMS Cluster
satellite booting). The file specification is limited to 127 characters.
If no file name is specified, OpenVMS Cluster satellite loads default
to APB.EXE where the boot type is set to ALPHA and NISCS_LOAD.EXE where
the boot type is set to VAX.
If you do not specify the /FILE qualifier, the setting remains
unchanged. The /NOFILE qualifier clears the field.
/IP_ADDRESS=value
/NOIP_ADDRESS
Associates an IP address with the node name. Specify the address in the
standard dotted notation, xxx.xxx.xxx.xxx.
If you do not specify the /IP_ADDRESS=value qualifier, the
setting remains unchanged. The /NOIP_ADDRESS qualifier clears the filed.
/PERMANENT_DATABASE (SET NODE only)
Updates the node entries in the LAN volatile node 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.
/ROOT=directory-specification
/NOROOT
Supplies the directory specification to be associated with the file
name. For cluster satellite service, the /ROOT qualifier specifies the
satellite root directory. For noncluster service, this qualifier
specifies the location of the file. If the file specification or the
file name given in the boot request includes the directory name, this
qualifier is ignored. The directory specification is limited to 127
characters.
If you do not specify the /ROOT qualifier, the setting remains
unchanged. The /NOROOT qualifier clears the field.
/SIZE=value
/NOSIZE
Specifies the size in bytes of the file data portion of each downline
load message. The default is the load data size specified for the
device. The permitted range is 246 to 1482 bytes. Use a larger size for
better load performance and less server overhead.
If you do not specify the /SIZE qualifier, the setting remains
unchanged. The /NOSIZE qualifier clears the setting.
/V3
/NOV3
Indicates that only MOP Version 3 formatted messages are to be used for
downline load purposes, regardless of the requested format. This allows
systems to load that have a problem with MOP Version 4 booting. This
qualifier causes the requesting node to fail over from MOP Version 4 to
MOP Version 3 when no response has been made to a MOP Version 4 load
request.
If you do not specify the /V3 qualifier, the setting remains unchanged.
The /NOV3 qualifier clears the setting.
/VOLATILE_DATABASE (DEFINE NODE only)
Updates the node entries in the LAN permanent node 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.
Examples
| #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.
SHOW ACP
Displays the current settings for LANCP and LANACP.
Format
SHOW ACP
Parameters
None.
Qualifiers
/OUTPUT=file-name
Creates the specified file and directs output to it.
Example
|
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.
SHOW CONFIGURATION
Displays a list of LAN devices and characteristics on the system.
Format
SHOW CONFIGURATION
Parameters
None.
Qualifiers
/OUTPUT=file-name
Creates the specified file and directs output to it.
/USERS
Shows which protocols are using which template device.
Example
|
LANCP> SHOW CONFIGURATION/USERS
LAN Configuration:
Device Parent Medium/User Version Speed Duplex Size MAC Address Current Address Type
------ ------ ----------- ------- ----- ------ ---- ----------------- ----------------- ----
EIA0 CSMA/C X-43 100 Full 1500 00-02-A5-20-00-A3 AA-00-04-00-CD-4C 82559
EIA3 60-03 DNA Routing 1498
EIA31 08-00-2B-60-01 MOP Dump/Load 1492
EIA32 60-01 MOP Dump/Load 1498
EWA0 CSMA/CD X-36 1000 Full 1500 00-10-18-04-30-26 00-10-18-04-30-26 BCM5703
EWB0 CSMA/CD X-110 100 Full 1500 00-30-6E-4A-37-64 00-30-6E-4A-37-64 DE500
EWC0 CSMA/CD X-46 1000 Full 1500 00-60-CF-21-82-08 00-60-CF-21-82-08 DEGPA
EWD0 CSMA/CD X-36 100 Full 1500 00-02-A5-20-7F-AB 00-02-A5-20-7F-AB BCM5703
EWE0 CSMA/CD X-110 10 Full 1500 00-30-6E-46-4C-30 00-30-6E-46-4C-30 DE500
EWF0 CSMA/CD X-110 10 Full 1500 00-30-6E-46-4C-31 00-30-6E-46-4C-31 DE500
EWG0 CSMA/CD X-110 10 Full 1500 00-30-6E-46-4C-32 00-30-6E-46-4C-32 DE500
EWH0 CSMA/CD X-110 10 Full 1500 00-30-6E-46-4C-33 00-30-6E-46-4C-33 DE500
EIB0 CSMA/CD X-9 1000 Full 1500 00-30-6E-5D-A3-4E 00-30-6E-5D-A3-4E Intel82540
EIC0 CSMA/CD X-9 1000 Full 1500 00-30-6E-5D-A3-4F 00-30-6E-5D-A3-4F Intel82540
|
|
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.
SHOW DEVICE
Displays information in the volatile device database. If the LANACP
process is not running, displays a list of current LAN devices.
Format
SHOW 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 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.
Note
If you do not specify a qualifier, the utility displays the matching
devices without additional information.
|
Qualifiers
/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.
Examples
| #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
|
|
