HP OpenVMS Systems Documentation
Content starts here

OpenVMS System Manager's Manual
Previous Contents Index

24.5.3 Setting Device Characteristics

All LAN devices are characterized by a collection of parameters. The parameters define the operational characteristics of a LAN device on the medium to which the device is connected.

To set LAN device parameters directly, enter the SET DEVICE command at the LANCP> prompt. The LANCP utility issues this command to the LANACP server process, which then issues the appropriate QIOs to set the driver characteristics.

The syntax for the SET DEVICE command is:


SET DEVICE device-name [/qualifiers]

Table 24-9 provides a brief description of the SET DEVICE command qualifiers that apply directly to LAN devices.

Table 24-9 DEFINE DEVICE and SET DEVICE Command Qualifiers
Qualifier Description
/AGING_TIMER= value Sets the amount of time in seconds to age source routing cache entries before marking them stale.
/ALL Sets data for all LAN 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)
/CACHE_ENTRIES= value Sets the number of entries to reserve for caching source routing address entries.
/CLIP++ Sets up 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 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=device,

 name="ip subnet name",

 enable, disable

 type = client|server)

The meanings of the syntax for /CLIP are as follows:

  • ip_address

    Specifies the IP address of the CLIP client.

  • subnet_mask

    Specifies the subnet mask of the CLIP client.

  • parent

    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 meanings for /CLIP are as follows:

Keyword Meaning
Create Loads the classical IP driver but does not start it.
Enable Causes the node to join the logical IP subnet.
Disable Causes the node to leave the logical IP subnet.
/CONTENDER Specifies that the device is to participate in the monitor contention process when it joins the ring.
/DISCOVERY_TIMER= value Sets the number of seconds to wait for a reply from a remote node when performing the source routing route discovery process.
/DLL=( enable-option, exclusive-option, size-option, knownclientsonly-option) Provides the MOP downline load service settings for the device.

In this qualifier, you can specify:

  • enable-option

    Indicates that MOP downline load service should be enabled or disabled for the device.

  • exclusive-option

    Indicates that no other provider of MOP downline load service is allowed on the specified LAN device at the same time as LANACP.

  • knownclientsonly-option

    Indicates that MOP downline load requests should be serviced only for clients defined in the LAN volatile node database.

  • size-option

    Specifies the size in bytes of the file data portion of each downline load message.

/EARLY Enables Early Token Release on the device.
/ELAN++ Sets LAN emulation. The /ELAN qualifier has two values: enable and disable. With /ELAN=ENABLE with the keyword STARTUP, the LAN emulation is loaded when LANACP starts. With /ELAN=DISABLE, the same parameters as ENABLE can be used.

The /ELAN qualifier's syntax is as follows: 

SET 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 are as follows:

  • parent

    The ATM adapter device name. An example of the parent device for DGLTA is: HC n0, where n is the controller number. An example of the parent device for DAPCA is: HW 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. 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
Create Loads the emulation driver SYS$ELDRIVER.EXE, but does not start it.
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.
/FULL_DUPLEX Enables full-duplex operation of a LAN device.
/MAP=(MULTICAST_ADDRESS=address,
FUNCTIONAL_ADDRESS=address) 		Defines a functional address mapping entry.
/MAX_BUFFERS= value Sets the maximum number of receive buffers to be allocated and used by the LAN driver for the LAN device.
/MEDIA= value
  • For Token Ring devices:

    Selects the type of cable that is being used to connect the adapter to the Token Ring Media Access Unit (MAU) for devices that do not automatically detect this.

  • For Ethernet devices:

    Selects the cable connection.

/MIN_BUFFERS= value Sets the minimum number of receive buffers to be allocated and used by the LAN driver for the LAN device.
/PERMANENT_DATABASE (SET command only) Updates the device entries in the LAN volatile device database with any data currently set in the permanent database.
/PVC=(vci[,...])++ Defines the permanent virtual circuit (PVC). 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. PVC has to be setup manually in the ATM switch.

The vci is the VCI (Virtual Circuit ID) of the PVC.

/NOPVC=(vci[,...])++ Does not set the permanent virtual circuit (PVC).
/RING_PURGER++ Enables the ring purging process of the FDDI device.
/SOURCE_ROUTING++ Enables source routing on the Token Ring device.
/SPEED= value Sets the speed of the LAN, if multiple speeds are supported.
/SR_ENTRY=(LAN_ADDRESS= address,
RI= routing-information) 		Statically defines a specific source-routed route for a specific node.
/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 one of the LAN device databases to that database. The DEFINE DEVICE command applies to the permanent database; the SET DEVICE command applies to the volatile database.
/VOLATILE_DATABASE (DEFINE command only) Updates the device entries in the LAN permanent device database with any data currently set in the volatile database.
++Alpha only

Examples 


  1. LANCP> SET DEVICE/CONTENDER/MEDIA=UTP/NOEARLY/SOURCE ICA0

    This command enables monitor contention, UTP cable media, and source routing, and disables early token release for Token Ring device ICA0. 


  2. LANCP> SET DEVICE/MEDIA=TWIST EWB0

    This command sets the media type to twisted pair for the second Tulip Ethernet device. 


  3. LANCP> SET DEVICE/ALL/MIN_BUFFERS=12

    This command sets the number of receive buffers for all LAN devices to be no less than 12. 


  4. LANCP> DEFINE DEVICE EXA0/MOPDLL=(ENABLE,EXCLUSIVE)

    This command defines LAN device EXA0 to enable LANACP MOP downline load service in exclusive mode. The settings 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 will be set to the defaults. 


  5. 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. 


  6. 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 FXA0 in exclusive mode for only known clients

24.6 Managing the LAN Device Databases

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, as follows:

  • 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.

The following sections describe how to enter and remove devices from the LAN permanent and volatile device databases, and how to enable and disable MOP downline load services.

24.6.1 Displaying Devices in the LAN Device Databases

To display information in the LAN permanent device database, enter the LIST DEVICE command using the following syntax:


LIST DEVICE device-name [/qualifiers]

To display information in the LAN volatile device database, enter the SHOW DEVICE command using the following syntax:


SHOW DEVICE device-name [/qualifiers]

Table 24-10 provides a brief description of the LIST DEVICE and SHOW DEVICE qualifiers.

Table 24-10 LIST DEVICE and SHOW DEVICE Command Qualifiers
Qualifier Description
/ALL Lists, or shows all devices which match device names.
/CHARACTERISTICS Same as the /PARAMETER qualifier.
/COUNTERS+ Displays device counters.
/DLL Lists or shows downline load characteristics.
/MAP Displays the current configuration of the functional address mapping table.
/MOPDLL Same as DLL.
/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 adapter, if available or applicable.
/SR_ENTRY Displays the contents of the current source routing cache table.
+SHOW DEVICE only
++Alpha only

Note
If you do not specify a qualifier, the utility displays the matching devices without additional information.

24.6.2 Entering Devices into the LAN Device Databases

To enter a device into the LAN permanent device database or to modify an existing entry, enter the DEFINE DEVICE command using the following syntax:


DEFINE DEVICE device-name [/qualifiers]

To enter a device into the LAN volatile device database or to modify an existing entry, enter the SET DEVICE command using the following syntax:


SET DEVICE device-name [/qualifiers]

24.6.3 Deleting Devices from the LAN Device Databases

To delete a device from the LAN permanent device database, enter the PURGE DEVICE command using the following syntax:


PURGE DEVICE device-name [/ALL]

To delete a device from the LAN volatile device database, enter the CLEAR DEVICE command using the following syntax:


CLEAR DEVICE device-name [/ALL]

For the PURGE DEVICE and CLEAR DEVICE commands, the /ALL qualifier deletes all LAN devices in the LAN permanent device database.

Examples 


  1. LANCP> PURGE DEVICE/ALL

    This command deletes all devices from the LAN permanent device database. 


  2. LANCP> CLEAR DEVICE EXA0

    This command deletes device EXA0 from the LAN volatile device database.

24.7 Managing the LAN Node Databases

The LAN volatile and permanent node databases contain a single entry for each defined LAN node. Each entry in the LAN volatile node database contains node information and MOP downline load counters information. Each entry in the LAN permanent node database contains node information that is used to populate the volatile database when the LANACP LAN server process is started.

Typically, each database contains the same nodes. The LANACP LAN server process maintains the volatile node database. The LANCP utility maintains the permanent node database. You can manipulate either database using the LANCP utility commands depending on your user privileges, as follows:

  • Privileged users can add or delete node entries from each database and clear MOP downline load counters information for LAN nodes
  • Unprivileged users can view the node information and MOP downline load status and counters information

The following sections describe how to enter nodes into and remove nodes from the LAN permanent and volatile node databases.

24.7.1 Displaying Nodes in the LAN Node Databases

To display information in the LAN permanent node database, enter the LIST NODE command using the following syntax:


LIST NODE node-name [/ALL]

To display information in the LAN volatile node database, enter the SHOW NODE command using the following syntax:


SHOW NODE node-name [/ALL]

For the LIST NODE and SHOW NODE commands, the /ALL qualifier displays data for all nodes in the LAN permanent or volatile node database.

24.7.2 Entering Nodes into the LAN Node Databases

To enter a node into the LAN permanent node database or to modify an existing entry, enter the DEFINE NODE command using the following syntax:


DEFINE NODE node-name [/qualifiers]

To enter a node into the LAN volatile node database or to modify an existing entry, enter the SET NODE command using the following syntax:


SET NODE node-name [/qualifiers]

Table 24-11 provides a brief description of the DEFINE NODE and SET NODE command qualifiers.

Table 24-11 DEFINE NODE and SET NODE Command Qualifiers
Qualifier Description
/ADDRESS= node-address Associates a LAN address with the node name.
/ALL Defines data for all nodes in the LAN permanent or volatile node database.
/BOOT_TYPE=VAX_SATELLITE| ALPHA_SATELLITE|OTHER Indicates the type of processing required for downline load requests.
/FILE= file-spec Supplies the file name you want to be provided when the downline load request does not include a file name.
/PERMANENT_DATABASE (SET command only) Updates the node entries in the LAN volatile node database with any data currently set in the permanent database.
/ROOT= directory-specification Supplies the directory specification to be associated with the file name.
/SIZE= value Specifies the size in bytes of the file data portion of each downline load message.
/V3 Forces the server to respond to only MOP Version 3 boot requests from this node.
/VOLATILE_DATABASE (DEFINE command only) Updates the node entries in the LAN permanent node database with any data currently set in the volatile database.

Examples 


  1. 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 system.
    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. 


  2. 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 system.
    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. 


  3. 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 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 a 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.

Previous Next Contents Index