![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
For more detailed information, see the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems and the OpenVMS System Management Utilities Reference Manual: A--L.
Classical IP (CLIP) over an ATM network is managed by using special LANCP command qualifiers. It is important to note that the /ATMADDRESS qualifier used with the LANCP DEFINE DEVICE and SET DEVICE commands needs to be manually set. This means the address resolution protocol (ARP) server must be set up before any clients are set up. There is only one ARP server for each logical IP subnet (LIS). A node that is set up as the ARP server automatically is set up as a client.
Also note that to determine the ATM address of the ARP server, the LANCP SHOW DEVICE command with the /CHARACTERISTICS qualifier needs to be invoked. As soon as the ATM ARP server is set up, the clients on other systems may be set up by specifying the ATM address of the ARP server with the LANCP SET DEVICE command.
The LANCP qualifiers are presented in the following sections.
Table 3-7 shows the CLIP qualifiers for the DEFINE DEVICE command.
| Qualifier | Description |
|---|---|
| /ATMADDRESS |
On Alpha systems, defines the LAN address resolution protocol (ARP)
server address for ATM. This qualifier is required before a logical IP
subnet (LIS) is enabled if the local host is not the ARP server. The
/ATMADDRESS qualifier's syntax is as follows:
DEFINE DEVICE/ATMADDRESS=(ARP=atm_arp_server)
|
| /CLIP |
On Alpha systems, the /CLIP qualifier defines a device with the TCP/IP
protocol. This enables the device to see a network as being configured
as one or more logical IP subnets (LIS) and allows it to transmit
Ethernet frames over the ATM network. The /CLIP=ENABLE command causes
the system to join the logical IP subnet when LANCP initializes. The
/CLIP=DISABLE command causes the client to leave the logical IP subnet.
Note that a logical IP subnet requires a server, and there must be only one server for each subnet. Communication between subnets can only be performed by a router. Also, there can only be one client for each ATM adapter. The /CLIP qualifier's syntax with standard Internet dotted notation is as follows: DEFINE DEVICE/CLIP=(ip_subnet=a.b.c.d,
|
| /CLIP (continued) |
The meanings for the syntax of keyword and subkeyword for /CLIP are as
follows:
|
For more detailed information, see the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems and the OpenVMS System Management Utilities Reference Manual: A--L.
| Qualifier | Description |
|---|---|
| /ALL | Lists all devices that match device names. |
| /CHARACTERISTICS | Same as the /PARAMETERS qualifier. |
| /PARAMETERS | Displays status and related information about the device. |
For more detailed information, see the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems and the OpenVMS System Management Utilities Reference Manual: A--L.
Table 3-9 shows the qualifiers for the LANCP SET DEVICE command that support CLIP.
| Qualifier | Description |
|---|---|
| /ATMADDRESS |
On Alpha systems, sets the address resolution protocol (ARP) server
address for ATM. This qualifier is required before a LIS is enabled if
the local host is not the ARP server. The /ATMADDRESS qualifier's
syntax is as follows:
SET DEVICE/ATMADDRESS=(ARP=atm_arp_server)
|
| /CLIP |
On Alpha systems, the /CLIP qualifier sets a device with the TCP/IP
protocol. This enables the device to see a network as being configured
as one or more logical IP subnets (LIS) and allows it to transmit
Ethernet frames over the ATM network. The /CLIP=ENABLE command causes
the system to join the logical IP subnet when LANCP initializes. The
/CLIP=DISABLE command causes the client to leave the logical IP subnet.
Note that a logical IP subnet requires a server, and there must be only one server for each subnet. Communication between subnets can only be performed by a router. Also, 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 =(create,ip_subnet=a.b.c.d,
The meanings for the syntax of keyword and subkeyword for /CLIP are as follows:
|
| /CLIP (continued) |
|
| /PERMANENT | Reads the permanent database and creates device entries in the volatile database. |
For more detailed information, see the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems and the OpenVMS System Management Utilities Reference Manual: A--L.
Table 3-10 shows the CLIP qualifiers for the SHOW DEVICE command.
| Qualifier | Description |
|---|---|
| /ALL | Shows all devices that match device names. |
| /CHARACTERISTICS | Same as the /PARAMETERS qualifier. |
| /PARAMETERS | Displays status and related information about the device. |
For more detailed information, see the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems and the OpenVMS System Management Utilities Reference Manual: A--L.
The /[NO]UNSHELVE qualifier controls how the Backup utility designates files from a BACKUP save operation: shelved or unshelved. File shelving migrates specific file data to offline storage transparently --- the data is still available and appears as if it were still online. This allows you to easily bring the file data back online, when necessary.
The /UNSHELVE qualifier specifies that the Backup utility designate files from a BACKUP save operation as unshelved, which means the data is available in an online state. A shelved file contains no actual file data. However, the file header remains intact and online. The default behavior is unshelved except during BACKUP save operations that require the /PHYSICAL or /IMAGE qualifier. For those operations, the files remain in their original file shelving state.
For more information about file shelving, refer to the POLYCENTER Hierarchical Storage Management (HSM) for OpenVMS documentation.
With OpenVMS Version 7.1, the right to use DECamds is provided with the OpenVMS operating system base license. Previously, the right to use DECamds was provided with the OpenVMS Cluster Software license. Now you can use all the system management capabilities provided by DECamds in a non-clustered environment.
DECamds is a separately installable, realtime, high-performance, multisystem monitoring utility. DECamds provides system resource monitoring, investigation aid, and correction capability. This enables system managers to proactively and effectively manage multiple systems from a centralized DECwindows display.
The DECamds kit can be installed on systems running OpenVMS Version 6.1 and later. For information on how to use DECamds to monitor your system resources, see the DECamds User's Guide.
The OpenVMS System Manager's Manual contains additional information about each new feature in this section.
You can now write the system dump file to a device other than the system disk. This feature is especially useful in large memory systems and in clusters with common system disks where sufficient disk space, on one disk, is not always available to support dump file requirements.
DOSD requirements are somewhat different on VAX and Alpha systems. On both systems, however, you must correctly enable the DUMPSTYLE system parameter to enable the bugcheck code to write the system dump file to an alternate device.
On Alpha systems, the contents of memory-resident error log buffers are now written not only to the system dump file but also to the new error log dump file. When an operator-initiated shutdown occurs, the contents of error log buffers are written only to the error log dump file, not to the system dump file. This means that when an operator initiates shutdown, the last system crash dump is not overwritten.
The error log dump file, SYS$SPECIFIC:[SYSEXE]SYS$ERRLOG.DMP, is not provided on the distribution kit; AUTOGEN creates this file during installation. AUTOGEN also automatically determines the appropriate size of the error log dump file for your configuration and system parameters. The error log dump file must always be on the system disk.
On Alpha systems, a new category of processes, key processes, are dumped immediately following PT (page table) space, S0/S1 space, and S2 space. These dumps also include transition pages that link back to the key process. The system manager can designate additional processes to be treated as key processes, have priority over other processes in a dump. Designating key processes ensures that any critical information provided by these processes is successfully written to the dump file, even when it is too small to contain information about all processes.
See the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems for instructions on how to designate the order of processes within a system dump.
OpenVMS Version 7.1 provides support for external authentication. The PATHWORKS authentication module is supported as an external authenticator, providing LAN Manager authentication of OpenVMS users. (PATHWORKS for OpenVMS Version 5.0D is required.) This is expected to be the first of several authentication modules which will be available in future releases of OpenVMS.
External authentication with LAN Manager allows users to log in at the OpenVMS login prompt using their LAN Manager user IDs and passwords. When successfully authenticated, the LAN Manager user ID is mapped to the appropriate OpenVMS user name and the correct user profile is obtained.
Before users can use external authentication, it must be enabled on the system and the user accounts in the system user authorization file (SYSUAF) must be marked for external authentication. These tasks are discussed in the following section.
External authentication is controlled at two levels:
$ DEFINE/SYSTEM/EXECUTIVE SYS$ACME_MODULE SYS$SHARE:PWRK$ACME_MODULE.EXE $ INSTALL ADD SYS$ACME_MODULE /OPEN/HEAD/SHARE $ DEFINE/SYSTEM/EXECUTIVE SYS$SINGLE_SIGNON 1
ADD username /FLAG=([NO]EXTAUTH) MODIFY username /FLAG=([NO]EXTAUTH)
By default, external authentication is disabled at both the system and user levels.
External authentication cannot occur if the network connection required for the authentication is down. However, privileged users can enter the /LOCAL_PASSWORD qualifier after their OpenVMS user name at the login prompt to inform OpenVMS that local authentication is to be performed. Users should specify their OpenVMS user name and password when using the /LOCAL_PASSWORD qualifier.
Because the use of the /LOCAL_PASSWORD qualifier is effectively overriding the security policy established by the system manager, it is only allowed under the following conditions:
For more information on the /LOCAL_PASSWORD qualifier to LOGINOUT, see the OpenVMS Utility Routines Manual.
If you are an externally authenticated user, the DCL command SET PASSWORD sends the password change request to the external authenticator and also changes your password on your OpenVMS system.
A system manager can set an externally authenticated user's password by using a utility provided by the external authenticator. In the case of LAN Manager, PATHWORKS provides a NET PASSWORD command. Using this method, the new password is propagated to the network immediately.
External authentication allows a user who is logging in to OpenVMS to be authenticated by an external entity (such as the PATHWORKS authentication module). OpenVMS does not check the SYSUAF to validate the user's password.
To be authenticated using LAN Manager user IDs and passwords, an externally authenticated user provides his or her LAN Manager user ID and password at the OpenVMS login prompt. The user IDs and passwords are used for authentication by a LAN Manager domain controller. When performing user name mapping, OpenVMS first tries to locate a match in the SYSUAF and uses that name if it finds a match; otherwise, it searches the LAN Manager database for a matching user ID. When successfully authenticated, the LAN Manager user ID is mapped to the appropriate OpenVMS user name to obtain the correct user profile, and the login sequence is completed.
External authentication is supported for interactive logins (including DECwindows) and network logins where a proxy is used or user ID/password is supplied.
Externally authenticated users are considered to have a single password and are not subject to normal OpenVMS password policy (password expiration, password history, minimum and maximum password length restrictions), but are instead subject to any defined LAN Manager policy. All other OpenVMS account restrictions remain in effect, such as disabled accounts, modal time restrictions, quotas, and so on.
Externally authenticated users are identified by having the EXTAUTH flag set in their SYSUAF record. OpenVMS users whose accounts do not have the EXTAUTH flag set are not affected by external authentication.
Although passwords for externally authenticated users are verified using the LAN Manager database, OpenVMS attempts to keep the LAN Manager and SYSUAF password fields synchronized. This synchronization occurs from LAN Manager to the SYSUAF.
Password synchronization is enabled by default.
Synchronization takes place at the completion of a successful externally authenticated login. If the LAN Manager password is different than the password stored in the SYSUAF file, LOGINOUT attempts to update the SYSUAF password field with the LAN Manager password. (Synchronization may not be possible due to the different sets of valid characters allowed by OpenVMS and LAN Manager.)
If required, the password synchronization feature can be selectively turned off. (See the Managing System Access chapter in the OpenVMS Guide to System Security for more information on the SYS$SINGLE_SIGNON logical name bits, which control the enabling and disabling of password synchronization.)
For more detailed information, see the OpenVMS Guide to System Security.
Fast Ethernet (802.3u), also known as 100BaseT, is an extension of the regular Ethernet 10BaseT standard. Fast Ethernet raises the data transmission capacity of 10BaseT from 10Mb/s to 100Mb/s while retaining Carrier Sense Multiple Access with Collision Detection (CSMA/CD) transmission protocol of 10BaseT Ethernet. Fast Ethernet works with several different types of cable including basic twisted-pair wiring. Because Fast Ethernet is a continuation of the former Ethernet standard, the same procedures, network analysis tools, and applications that run with the 10BaseT Ethernet network work with the 100BaseT network.
Table 3-11 shows the types of cabling that Fast Ethernet uses.
| Cable | Description |
|---|---|
| 100BaseTX | Works with twisted-pair cabling standards. It provides full-duplex performance with network servers, using only two of the four pairs of wires. |
| 100BaseT4 | Works with twisted-pair cabling standards. It uses four pairs of wiring with one pair for transmission, another for reception, and two pairs that can be used to either transmit or receive data. It does not support full-duplex operations. |
| 100BaseFX | Uses fiber optic cabling mainly for backbones by connecting Fast Ethernet repeaters placed around a building. It gives protection from electromagnetic noise and increases security. It also allows longer distances between network devices. |
The end-to-end diameter or segment diameter of a network for Fast Ethernet is limited to 250 meters. The 10Mb/s Ethernet network has a limit of 2,500 meters. Fast Ethernet adheres to the 10BaseT rule that a computer can be no more than 100 meters from a hub.
OpenVMS Version 7.1 supports the following two adapters:
Each of these adapters may be run at 10Mb/s or 100Mb/s. The 10Mb/s or 100Mb/s transmission rate is determined when the driver is started.
For more detailed information, see the OpenVMS I/O User's Reference Manual.
OpenVMS Alpha Version 7.1 device driver support of high SCSI IDs allows host adapters that support the wide SCSI bus to configure and use up to 16 devices per SCSI bus.
KZTSA, KZPSA, and the QLogic wide adapters (including KFTIA fast wide differential ports, KZPDA, KZPSM, and the AlphaStation 600 embedded SCSI port) currently support high SCSI IDs.
Note that although the maximum allowable number of devices per SCSI bus has increased, the SCSI bus length requirements have not. When configuring devices above the previous limit of 8 devices, failure to adhere to bus length requirements can produce unpredictable results.
Supported SCSI bus lengths are as follows:
To configure wide IDs on a BA356 box, refer to the BA356 manual StorageWorks Solutions BA356-SB 16-Bit Shelf User's Guide.
If you mix narrow and wide devices on a wide bus, make sure that the hosts and all narrow devices have IDs in the 0 to 7 range. Do not install narrow devices in a storage shelf that is configured for IDs in the range of 8 to 15.
OpenVMS Version 7.1 supports the following new LANCP utility commands:
These commands convert earlier LANCP database formats to the current Version 7.1 format. Note that although both LANCP and LANACP can read earlier database formats, entries can only be written in the Version 7.1 format.
The CONVERT DEVICE_DATABASE command converts an OpenVMS Version 6.2 format LANCP device database to an OpenVMS Version 7.1 format device database. This command requires SYSPRV privilege. This command has no parameters or qualifiers.
For more information, see the OpenVMS System Management Utilities Reference Manual: A--L.
The CONVERT NODE_DATABASE command converts an OpenVMS Version 6.2 format LANCP node database to an OpenVMS Version 7.1 format node database. This command requires SYSPRV privilege. This command has no parameters or qualifiers.
For more information, see the OpenVMS System Management Utilities Reference Manual: A--L.
The OpenVMS License Management Facility (LMF) offers the following new features:
Use the License Management utility (LICENSE), the command-line interface for managing software licenses, to implement these new features.
Table 3-12 shows the LICENSE qualifiers and options new for this release of the OpenVMS operating system.
| Command | Qualifier | Description |
|---|---|---|
| LICENSE LIST | /SELECTION_WEIGHT | Displays the current selection weight of a PAK. |
| LICENSE LOAD | /UNLOAD | Default. When requested to load a license that is currently loaded, LMF first automatically unloads it and then loads the latest license. |
| /NOUNLOAD | LMF does not unload the currently loaded license before loading the latest license. | |
| LICENSE MODIFY | /COMBINE | Adds the /COMBINE option to a PAK. If PAKs can be combined, LMF combines them during license loading. |
| /NOCOMBINE | Removes the /COMBINE option from a PAK. | |
| /SELECTION_WEIGHT= n | Modifies the current selection weight of a PAK. | |
| LICENSE REGISTER | /OPTIONS=VAX_ALPHA | Registers an Availability license that is valid for both OpenVMS VAX and OpenVMS Alpha systems. |
| /OPTIONS=USER | Designates a User license. |
6480P002.HTM OSSG Documentation 5-DEC-1996 13:49:21.12
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.