![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
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 ATMworks 350 is: HC n0, where n is the controller number. An example of the parent device for ATMworks 750 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, 9234, or 18,190 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 |
|---|---|
| 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. |
The /NOFULL_DUPLEX qualifier, disallows full-duplex operation regardless of the hardware configuration.
Devices: Devices that support full-duplex operation
The /NOMAP=(MULTICAST_ADDRESS=address) qualifier, clears the mapping established for the specified address.
Specify the functional address as follows:
For example, to map the multicast address CB-00-01-02-03-04 to the functional address 03-00-00-80-00-00 on the Token Ring device IRA0, enter the following command:
SET DEVICE IRA0/MAP=(MULTI=CB-00-01-02-03-04,FUNCT=00:01:00:00)
For the default address mapping, see Table 12-2 or issue the command SHOW DEVICE/MAP device-name.
| Multicast Address | Functional Address | Description |
|---|---|---|
| 09-00-2B-00-00-04 | 03-00-00-00-02-00 | ISO ALL ES |
| 09-00-2B-00-00-05 | 03-00-00-00-01-00 | ISO ALL IS |
| CF-00-00-00-00-00 | 03-00-00-08-00-00 | Loopback Assistant |
| AB-00-00-01-00-00 | 03-00-02-00-00-00 | DNA MOP Dump/Load |
| AB-00-00-02-00-00 | 03-00-04-00-00-00 | DNA MOP Remote Console |
| AB-00-00-03-00-00 | 03-00-08-00-00-00 | DNA L1 Routers |
| 09-00-2B-02-00-00 | 03-00-08-00-00-00 | DNA L2 Routers |
| 09-00-2B-02-01-0A | 03-00-08-00-00-00 | DNA Phase IV Primary Router |
| AB-00-00-04-00-00 | 03-00-10-00-00-00 | DNA Endnodes |
| 09-00-2B-02-01-0B | 03-00-10-00-00-00 | DNA Phase IV Prime Unknown Destination |
| 09-00-2B-00-00-07 | 03-00-20-00-00-00 | PCSA NETBIOS Emulation |
| 09-00-2B-00-00-0F | 03-00-40-00-00-00 | LAT Service Advertisement |
| 09-00-2B-02-01-04 | 03-00-80-00-00-00 | LAT Service Solicit |
| 09-00-2B-02-01-07 | 03-00-00-02-00-00 | LAT Xwindown Service Solicit |
| 09-00-2B-04-00-00 | 03-00-00-04-00-00 | LAST |
| 09-00-2B-02-01-00 | 03-00-00-00-08-00 | DNA Name Service Advertisement |
| 09-00-2B-02-01-01 | 03-00-00-00-10-00 | DNA Name Service Solicit |
| 09-00-2B-02-01-02 | 03-00-00-00-20-00 | DNA Time Service |
| 03-00-00-00-00-01 | 03-00-00-00-00-01 | NETBUI Emulation |
| 03-00-02-00-00-00 | 03-00-02-00-00-00 | RIPL |
Devices: Token Ring devices
Devices: All LAN devices
Devices: Any LAN device that has software-settable media selection
Devices: All LAN devices
Devices: Token Ring devices
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.
Devices: Token Ring devices and the DE500 Ethernet/Fast Ethernet device
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.
Devices: Token Ring devices
Examples
LANCP> SET DEVICE/CONTENDER/MEDIA=UTP/NOEARLY/SOURCE ICA0
LANCP> SET DEVICE/MEDIA=TWI EWB0
Enters a device into the LAN volatile device database or modifies an existing entry. Requires SYSPRV privilege.
SET DEVICE device-name
device-name
Specifies a device to be entered in the LAN volatile device database or an entry to be modified.
/ALL
Defines data for all LAN devices in the LAN volatile 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./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 implementation that operates the MOP protocol in shared mode).- knownclientsonly-option
KNOWNCLIENTSONLY
NOKNOWNCLIENTSONLY (default)
Specify KNOWNCLIENTSONLY to indicate that MOP downline load requests should be serviced only for clients defined in the LAN volatile node database. When NOKNOWNCLIENTSONLY is selected, LANACP searches the LAN$DLL directory for any images requested by clients that are not defined in the LAN volatile 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 DEFINE NODE and SET NODE for details./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./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
LANCP> SET DEVICE EXA0/MOPDLL=ENABLE
LANCP> SET DEVICE EXA0/MOPDLL=(ENABLE,EXCLUSIVE,SIZE=1482)
LANCP> SET DEVICE EXA0/MOPDLL=(ENABLE,NOEXCLUSIVE) LANCP> SET DEVICE FXA0/MOPDLL=(ENABLE,EXCL,KNOWN)
Enters a node into the LAN volatile node database or modifies an existing entry. Requires SYSPRV privilege.
SET NODE node-name
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.
/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: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.
- 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
If you do not specify the /BOOT_TYPE qualifier, the setting remains unchanged. The /NOBOOT_TYPE 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.
/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
LANCP> SET NODE VAXSYS/ADDRESS=08-00-2B-11-22-33 -
/FILE=APB.EXE -
/ROOT=$64$DIA14:<SYS10.> -
/BOOT_TYPE=ALPHA_SATELLITE
LANCP> SET NODE VAXSYS/ADDRESS=08-00-2B-11-22-33 -
/FILE=NISCS_LOAD.EXE -
/ROOT=$64$DIA14:<SYS10.> -
/BOOT_TYPE=VAX_SATELLITE
LANCP> SET NODE VAXSYS/ADDRESS=08-00-2B-11-22-33/NOROOT
SET NODE CALPAL/ADDRESS=08-00-2B-11-22-33/FILE=APB_061.EXE
Displays a list of LAN devices and characteristics on the system.
SHOW CONFIGURATION
None.
/USERS
On Alpha systems, shows which protocols are using which template device.
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.
6048P025.HTM OSSG Documentation 26-NOV-1996 12:42:55.82
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.