 |
OpenVMS System Management Utilities Reference
Manual
/MEDIA=value
- For Token Ring devices:
Selects the type of cable media used to
connect the adapter to the Token Ring Media Access Unit (MAU) for
devices that do not automatically detect this. Acceptable values for
this are either unshielded twisted pair (UTP) or shielded twisted pair
(STP). The default value is STP.
- For Ethernet devices:
Selects the cable connection. Normally,
the selection is made during device initialization using a limited
autosensing algorithm that selects twisted pair, but fails over to AUI
(Attachment Unit Interface) if twisted pair does not appear to be
functional. Thereafter, a cabling change would require a reboot of the
system to take effect. This command allows you to change the selection
without rebooting.
Acceptable values are AUI (10Base2, 10Base5),
TWISTEDPAIR (10BaseT), and AUTOSENSE (reperform the limited autosense
algorithm). The default value is AUTOSENSE.
Some devices, such as
the DE435, require a jumper change on the Ethernet card to switch
between 10Base2 and 10Base5 (thinwire and thickwire). Other devices,
such as the DE434, DE436, and DE500, have only twisted pair connections.
/MIN_BUFFERS=value
Sets the minimum number of receive buffers to be allocated and used by
the LAN driver for the LAN device.
/PERMANENT
Reads the permanent database and creates device entries in the volatile
database.
/PERMANENT_DATABASE
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.
/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.
/RING_PURGER
Enables the ring purger process of the FDDI device.
/SOURCE_ROUTING (default)
/NOSOURCE_ROUTING
Enables source routing on the Token Ring device. If you only have one
ring in your LAN or you use transparent bridging, use the
/NOSOURCE_ROUTING qualifier to turn off source routing.
/SPEED=value
Sets the speed of the LAN.
For Token Ring, 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 (as does the DEC Token Ring Controller 700).
For Ethernet, valid values are either 10 or 100, which selects the 10
megabits per second Ethernet port or the 100 megabits per second Fast
Ethernet port. The default for Ethernet is to sense automatically which
type of port is connected and select the appropriate speed.
/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.
/TOKEN_ROTATION
Sets the requested token rotation time for the FDDI ring.
/TOKEN_TIMEOUT
Sets the restricted token timeout time for the FDDI ring.
/TRANSMIT_TIMEOUT
Sets the valid transmission time for the FDDI device.
/UPDATE
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_DATABASE qualifier. You can combine the
/UPDATE and /PERMANENT_DATABASE qualifiers in a single SET DEVICE
command.
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
- 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.
/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
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.
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.
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
On Alpha systems, shows which protocols are using which template device.
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 example shows 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
(hardware or firmware) 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.
Consult your device-specific documentation to correlate the version
returned with a particular hardware or firmware implementation of the
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
On Alpha systems, same as the /PARAMETERS qualifier.
/COUNTERS
Displays device counters.
/DLL
Displays LAN volatile device database information related to MOP
downline load for the device.
/MAP
Displays the current configuration of the functional address mapping
table.
/MOPDLL
Same as the /DLL qualifier.
/OUTPUT=file-name
Creates the specified file and directs output to it.
/PARAMETERS
Displays status and related information about the device.
/REVISION
Displays the current firmware revision of the device, if available or
applicable. Not all LAN devices return revision information. LAN
devices that do not have a revision display a revision of zero.
/SR_ENTRY
Displays the contents of the current Token Ring source routing cache
table.
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
|
This command displays MOP downline load information in the LAN volatile
device database for device EXA0.
| #5 |
LANCP> SHOW DEVICE/PARAMETERS IRA0
Device Parameters IRA0:
Value Parameter
----- ---------
Normal Controller mode
External Internal loopback mode
00-00-93-58-5D-32 Hardware LAN address
Token Ring Communication medium
Enabled Functional address mode
No Full duplex enable
No Full duplex operational
16 Line speed (megabits/second)
16 Mbps Ring speed
STP Line media
Enabled Early token release
Disabled Monitor contender
200 SR cache entries
2 SR discovery timer
60 SR Aging Timer
Enabled Source routing
3 Authorized access priority
AA-00-04-00-92-FF Upstream neighbor
0 Ring number
|
This command displays status and parameters information for Token ring
device IRA0.
| #6 |
LANCP> SHOW DEVICE/REVISION FXA0
Device revision FXA0: 05140823
|
This command displays revision information for FDDI device FXA0.
| #7 |
LANCP> SHOW DEVICE/SR_ENTRY ICA0
Source Routing Cache Table ICA0:
LAN address State XmtTmo RcvTmo StaleTmo DiscvTmo
----------------- ----- -------- -------- -------- --------
AA-00-04-00-92-FF LOCAL 00000028 00000028 00000245 00000000
|
This command displays source routing entry information for Token Ring
device ICA0.
|
