HP OpenVMS Systems Documentation
HP OpenVMS Version 8.4 New Features and Documentation Overview
Specifies whether the mapping is global or local. You are provided two
options for this directive:
indicates that global mapping is enabled for the user.
If mapping directive is not used, mapping will be one-to-one.
This directive is applicable only for global mapping.
Set this to the attribute on directory server that is used for user mapping.
can be referenced to description field for the user in the directory
You can also use any newly created attribute on the directory server for mapping. The attribute should be an IA5 multi-valued string.
This directive is applicable only for global mapping. The
is searched in the value of directory server's
Consider that the LDAP INI file has the following attributes:
Consider that the "description" attribute in the Directory Server be populated with: VMSUsers.hp.com/jdoe
The ACME LDAP agent then searches in "VMSUsers.hp.com/jdoe", for a prefix of "VMSUsers.hp.com/" (With a forward slash (/) along with the mapping_target). The rest of the value that is, "jdoe" is considered as the user name present in SYSUAF.DAT file.
If a multi-valued string attribute is used, the "VMSUsers.hp.com/jdoe" must be one of the array elements of the multi-valued string.
This directive is applicable only for local mapping. Set this to the
complete path of the text database file to be searched for mapping
A template file is present in SYS$STARTUP:LDAP_LOCALUSER_DATABASE.TXT_TEMPLATE. This file includes the LDAP username and VMS usernames separated by a comma, where LDAP username is the name of the user in the domain (entered at the username prompt during login).
For information on how to populate and load the contents of the database file, see SYS$STARTUP:LDAP_LOCALUSER_DATABASE.TXT_TEMPLATE.
Examples for global mapping
Two users, John Doe and Joe Hardy have the following attributes specified in the user profile of the Active directory:
DN: cn=john doe,...
samaccountname: John Doe
In the SYSUAF.DAT file, the username is "jdoe" and "jhardy".
In global mapping:
mapping = server mapping_attribute = description mapping_target = VMSusers.hp.com
SET SERVER ACME/RESTART
Examples for local mapping
Two users John Doe and Joe Hardy have the following attributes specified in the user profile of the Active directory:
DN: cn=john doe,...
samaccountname: John Doe
mapping = local mapping_file = SYS$COMMON:[SYS$STARTUP]LDAP_LOCALUSER_DATABASE.TXT
$ SET SERVER ACME/RESTART
$ load_localuser_db:=="$SYS$SYSTEM:LDAP_LOAD_LOCALUSER_DATABASE.EXE" $ load_localuser_db SYS$COMMON:[SYS$STARTUP]LDAP_LOCALUSER_DATABASE.TXT
This chapter provides information about the new features, changes, and
enhancements for system management functionality.
8.1 Provisioning Enhancements using HP SIM
Provisioning has been enhanced to deploy OpenVMS Version 8.4 on
selected Integrity servers from HP SIM. Provisioning allows you to
install OpenVMS Version 8.4, or upgrade to OpenVMS Version 8.4 from a
previous version of OpenVMS by using InfoServer or vMedia. For more
information about deployment, see the HP OpenVMS Upgrade and
8.1.2 Configuring OpenVMS TCP/IP
Provisioning has been enhanced to configure HP TCP/IP Services for
OpenVMS on selected Integrity servers from HP SIM. Provisioning allows
you to configure the TCP/IP core environment, and client or server
components on up to eight OpenVMS Integrity servers simultaneously. An
OpenVMS server can be configured with static IP address settings or as
a dynamic host configuration protocol (DHCP) client. For more
information, see the HP OpenVMS Version 8.4 Upgrade and
8.2 WBEM Providers for OpenVMS Version 8.4
OpenVMS Version 8.4 adds support for the Integrated Lights Out (iLO) Integrated Remote Console capability provided by Integrity servers and BladeSystems supporting iLO. The enabling functionality that provides this support is referred to as virtual Keyboard, Video, and Mouse or vKVM.
The Integrated Remote Console capability allows the display from the built-in graphics chip to be viewed on a remote web browser connected to the iLO firmware on an Integrity server system. The mouse and keyboard on the computer are used to simulate a USB device on the Integrity server. As a result, a remote user can interact with an Integrity server as if they are using a local keyboard, video, and mouse transparently to the local system.
Text based VGA console and the DECwindows display are available in the iLO Integrated Remote Console window. A maximum DECwindows display resolution of 1024x768 (OpenVMS default) is imposed by the iLO firmware.
The iLO Integrated Console firmware transmits compressed images of changes on the screen over the network to a web browser, which limits performance and responsiveness. Because of this performance limitation, use of graphics intensive DECwindows is not recommended.
The local keyboard, video, and mouse and the remote Integrated Remote Console capability can be used simultaneously.
The vKVM enabling software on OpenVMS adds additional capabilities beyond the iLO Integrated Remote Console:
If Motif is installed, DECwindows starts on the systems that have a built-in graphics chip (the graphics chip is integrated with the management processor on Integrity servers) though the keyboard, mouse or monitor are not attached. DECwindows can be disabled by editing SYS$MANAGER:SYSTARTUP_VMS.COM. The symbol definition of DECW$IGNORE_DECWINDOWS must be un-commented to set it to TRUE.
Several pseudo devices, such as IMX0, IKX0, KBX0, and MOX0 are created
to enable vKVM.
8.4 CPU Component Indictment - Dynamic Processor Resilience
OpenVMS Version 8.4 supports CPU Component Indictment - Dynamic Processor Resilience (DPR) on Integrity servers. This feature was introduced for Alpha processors with OpenVMS Version 7.3-2. The component indictment process works in conjunction with HP Web-Based Enterprise Services (WEBES).
In addition to the existing features available on Alpha, Integrity server systems support the following features:
For information about support and usage of DPR, see the WEBES and iCAP
8.4.1 Enabling and Disabling the Indictment Server
SYS$MANAGER:SYS$INDICTMENT_POLICY.COM enables the system manager to
turn the indictment server and indictment mechanism on or off.
Indictment mechanism is a policy to enable or disable an attempt by the
operating system to STOP a CPU that has been indicted. By default, when
the indictment server is started, the indictment mechanism is disabled;
the system manager must manually modify SYS$INDICTMENT_POLICY.COM to
enable this feature. This requires a reboot of the system.
8.4.2 Displaying the Indicted CPU Status
OpenVMS Version 8.4 has added a new CPU state string to reflect the
state of the indicted CPU. Executing SHOW CPU/FULL on an indicted CPU
shows the new CPU state as "DEALLOCATED".
8.5 Power Management (Integrity servers Only)
OpenVMS has supported power savings on idle since Version 8.2-1 using the SYSGEN parameters, CPU_POWER_MGMT and CPU_POWER_THRSH. However, in OpenVMS Version 8.4, OpenVMS power management supports processor p-states, available on Intel Itanium processor 9100 series and later CPUs, to reduce power use while a CPU is not idle. OpenVMS also supports additional user and programming interfaces. On some platforms, OpenVMS Version 8.4 supports a power management interface from the iLO console and from the Insight Power Manager (IPM) software. A new system service $POWER_CONTROL is added on all Integrity server platforms. For information about the new system service, see the HP OpenVMS System Services Reference Manual.
OpenVMS Version 8.4 power management operates in an upward compatible manner on all platforms that do not fall into the category with IPM support. The performance of the idle power saving algorithm is improved. To enable idle power savings, the default value for the CPU_POWER_MGMT parameter is changed from 0 to 1.
For platforms that support iLO, the default firmware setting is Dynamic Power Savings, which, on OpenVMS, corresponds to the idle power saving algorithm.
In accordance with the standards used by all operating systems on Integrity servers, if you have an iLO or IPM power interface, that interface takes priority over other operating system interfaces. On OpenVMS systems, CPU_POWER_MGMT and $POWER_CONTROL are overridden by the iLO or IPM interface.
On OpenVMS guest systems, the default is low power mode and this behavior can not be changed.
Table 8-1 lists the power saving values that can be set using the iLO or IPM interface.
|Power Mode||Description||OpenVMS Implementation|
|Static high performance||The operating system makes no attempt to save power if there is any compromise in performance.||No power savings method used.|
|Static low power||The operating system saves power in every way it can, even to the detriment of performance.||On CPUs that support static low power, switch to the lowest p-state at all times. Also uses idle power savings on all CPUs.|
|Dynamic Power Savings||The operating system attempts to use lower power modes dynamically to save power while minimizing loss of performance.||Use idle power savings.|
|OS Control||The power savings mode is controlled by OS-specific mechanisms.||Enable the $POWER_CONTROL system service and the $CPU_POWER_MGMT SYSGEN parameter.|
The following system parameters have been added in this release:
The following new features are provided in the System Analysis Tools
utilities for OpenVMS Version 8.4.
8.7.1 Support for Partial Dump Copies
The "Partial Dump Copies" feature has been added to SDA. This feature takes advantage of the organization of a selective dump. In most cases, only a small part of the dump is needed to investigate the cause of the system crash. The system manager can save the complete dump locally, but only copy the key sections of the dump over the network to HP support. This can significantly reduce the time taken to copy the dump.
If information is needed from a section of the dump that was not copied, it can be extracted from the saved local copy and submitted separately. The ANALYZE /CRASH_DUMP command now accepts multiple input files from the same crash and treats them as a single dump.
For an explanation of key processes and key global pages, and the organization of a selective system dump, see the System Manager's Manual, Volume 2.
To create an initial partial dump copy and to extract an additional section, complete the following steps:
$ ANALYZE/CRASH SYS$SYSTEM:SYSDUMP.DMP OpenVMS system dump analyzer ...analyzing an I64 compressed selective memory dump... Dump taken on 22-SEP-2009 18:17:17.99 using version 8.4 SSRVEXCEPT, Unexpected system service exception SDA> COPY SSRVEXCEPT.DMP SDA> EXIT
$ ANALYZE/CRASH SSRVEXCEPT OpenVMS system dump analyzer ...analyzing an I64 compressed selective memory dump... Dump taken on 22-SEP-2009 18:17:17.99 using version 8.4 SSRVEXCEPT, Unexpected system service exception SDA> COPY/PARTIAL=KEY SSRVKEY SDA> EXIT
$ ANALYZE/CRASH SSRVKEY OpenVMS system dump analyzer ...analyzing an I64 compressed selective memory dump... Dump taken on 22-SEP-2009 18:17:17.99 using version 8.4 SSRVEXCEPT, Unexpected system service exception SDA> SHOW CRASH SDA> ! etc.
$ ANALYZE/CRASH SSRVEXCEPT OpenVMS system dump analyzer ...analyzing an I64 compressed selective memory dump... Dump taken on 22-SEP-2009 18:17:17.99 using version 8.4 SSRVEXCEPT, Unexpected system service exception SDA> COPY/PARTIAL=PROCESS=NAME=CLUSTER_SERVER SSRVCSP SDA> EXIT
$ ANALYZE/CRASH SSRVKEY,SSRVCSP OpenVMS system dump analyzer ...analyzing an I64 compressed selective memory dump... Dump taken on 22-SEP-2009 18:17:17.99 using version 8.4 SSRVEXCEPT, Unexpected system service exception SDA> SHOW PROCESS CLUSTER_SERVER SDA> ! etc.