HP OpenVMS Systems Documentation
HP OpenVMS Version 8.2 Release Notes
ODS-5 disks are also incompatible with versions of OpenVMS prior to Version 7.2.
The following table lists which versions of DECwindows Motif are supported on various platforms of the OpenVMS Version 8.2 operating system.
|OpenVMS Version||DECwindows Motif Version|
|OpenVMS I64 8.2||DECwindows Motif for OpenVMS I64 V1.5|
|OpenVMS Alpha 8.2||DECwindows Motif for OpenVMS Alpha V1.5|
The DECwindows Motif software relies on specific versions of OpenVMS server and device driver images. Be sure to install or upgrade to the version of DECwindows Motif that is appropriate to your operating system environment, as noted in Table 1-1.
For information on support for prior versions of DECwindows Motif, see the HP DECwindows Motif for OpenVMS Release Notes.
For detailed information about installing the DECwindows Motif
software, refer to the HP DECwindows Motif for OpenVMS Installation
1.7 HP SSL: Installing HP SSL V1.2
Installing HP SSL V1.2 on your Alpha or I64 system provides you with new ciphers and algorithms as well as the latest security fixes from openssl.org. The HP SSL V1.2 kit is included with the layered products distribution. HP recommends that you install HP SSL V1.2 after you install or upgrade your operating system and TCP/IP Services for OpenVMS.
You must manually remove any previous versions of SSL before installing SSL V1.2. Use the following commands to remove and install SSL:
$ PRODUCT REMOVE SSL $ PRODUCT INSTALL SSL /SOURCE=ddcu:[directory]
For details about installing and using SSL, refer to the HP Open Source Security for OpenVMS, Volume 2: HP SSL for OpenVMS
1.8 Release Notes for OpenVMS I64 Users
The following notes are primarily of interest to users of OpenVMS I64
1.8.1 HP Integrity Server Configurations
The OpenVMS I64 Version 8.2 release supports all of the standard system features and core I/O on the rx1600-2, rx1620-2, rx2600-2, rx2620-2, and rx4640-8 Integrity servers.
For OpenVMS I64 Version 8.2, there are two primary storage interconnects:
Customers who used any earlier evaluation or field test kits should note the following important considerations:
HP Integrity servers maintain a System Event Log (SEL) within system console storage, and OpenVMS I64 automatically transfers the contents of the SEL into the OpenVMS error log. If you are operating from the console during a successful boot operation, you might see a message indicating that the Baseboard Management Controller (BMC) SEL is full. You can safely continue when the BMC SEL is full by following the prompts; OpenVMS will process the contents of the SEL. If you wish to clear the SEL manually, enter the following command at the EFI Shell prompt:
Shell> clearlogs SEL
This command deletes the contents of the SEL. The command is available with current system firmware versions.
If your Integrity server is configured with a Management Processor (MP) and you see a BMC event log warning while connected to the MP console, you can clear the BMC event log by using MP. Press Ctrl/B to drop to the MP> prompt. At the MP> prompt, enter SL (from the main menu) and use the C option to clear the log.
HP recommends that you load and use the most current system firmware.
For more information about updating the system firmware, refer to the
HP OpenVMS Version 8.2 Upgrade and Installation Manual.
1.8.3 Firmware for Integrity Servers
OpenVMS I64 Version 8.2 was tested with the latest firmware for each of the supported Integrity servers. The following table lists the recommended firmware versions:
Some new rx4640 servers require, and will ship with, the higher firmware versions shown in the table. As this manual goes to press, the lower firmware versions are the latest released to customers to update existing servers. OpenVMS has been tested with both versions of firmware. HP recommends that all rx4640 servers be updated to the higher firmware versions when the firmware is released.
To check the firmware versions for your server, use the Extensible Firmware Interface (EFI) command INFO FW, as shown in the following example. (For instructions on how to access and use EFI, refer to the HP OpenVMS Version 8.2 Upgrade and Installation Manual.)
Shell> INFO FW FIRMWARE INFORMATION Firmware Revision: 2.13  (1) PAL_A Revision: 7.31/5.37 PAL_B Revision: 5.65 HI Revision: 1.02 SAL Spec Revision: 3.01 SAL_A Revision: 2.00 SAL_B Revision: 2.13 EFI Spec Revision: 1.10 EFI Intel Drop Revision: 14.61 EFI Build Revision: 2.10 POSSE Revision: 0.10 ACPI Revision: 7.00 BMC Revision: 2.35 (2) IPMI Revision: 1.00 SMBIOS Revision: 2.3.2a Management Processor Revision: E.02.29 (3)
The HP Integrity rx4640 server contains Dual Hot Plug Controller (DHPC) hardware with upgradable firmware. To check the current version of your DHPC firmware, use the EFI command INFO CHIPREV, as shown in the following example. The hot-plug controller version will be displayed. A display of 0100 indicates version 1.0; a display of 0110 means version 1.1.
Shell> INFO CHIPREV CHIP REVISION INFORMATION Chip Logical Device Chip Type ID ID Revision ------------------- ------- ------ -------- Memory Controller 0 122b 0023 Root Bridge 0 1229 0023 Host Bridge 0000 122e 0032 Host Bridge 0001 122e 0032 Host Bridge 0002 122e 0032 Host Bridge 0004 122e 0032 HotPlug Controller 0 0 0110 Host Bridge 0005 122e 0032 HotPlug Controller 0 0 0110 Host Bridge 0006 122e 0032 Other Bridge 0 0 0002 Other Bridge 0 0 0008 Baseboard MC 0 0 0235
For instructions on upgrading your firmware, refer to the HP OpenVMS Version 8.2 Upgrade and Installation Manual.
1.8.4 Booting On a Fibre Channel Storage Device
Many customers prefer to boot from a Fibre Channel (FC) storage device because of its speed and because it can serve as a common cluster system disk in a SAN. Booting on a FC storage device on OpenVMS I64 systems is significantly different from booting on a FC storage device on OpenVMS Alpha systems.
Refer to the Fibre Channel chapter of Guidelines for OpenVMS Cluster Configurations for directions on
how to configure and boot from a FC device on OpenVMS I64 systems.
1.8.5 Booting from the Installation DVD
On I64 systems with the minimum amount of supported memory (512MB), the following message appears when booting from the installation DVD:
********* XFC-W-MemmgtInit Misconfigure Detected ******** XFC-E-MemMisconfigure MPW_HILIM + FREEGOAL > Physical Memory and no reserved memory for XFC XFC-I-RECONFIG Setting MPW$GL_HILIM to no more than 25% of physical memory XFC-I-RECONFIG Setting FREEGOAL to no more than 10% of physical memory ********* XFC-W-MemMisconfigure AUTOGEN should be run to correct configuration ******** ********* XFC-I-MemmgtInit Bootstrap continuing ********
The message means that the system cache (XFC) initialization has
successfully adjusted the SYSGEN parameters MPW_HILIM and FREEGOAL to
allow caching to be effective during the installation. You can continue
with the installation.
1.8.6 Setting Up I64 Systems to Reboot
An I64 system does not automatically reboot unless it has been set up to do so from the console. In a cluster, the Alpha systems will reboot, but the I64 systems will shut down and sit at the console prompt.
For details about how to set up your I64 system to reboot, refer to the
HP OpenVMS Version 8.2 Upgrade and Installation Manual.
1.8.7 HP DECwindows Motif Release Notes
The following DECwindows Motif release notes are of interest to OpenVMS
126.96.36.199 Keyboard Support
The only model keyboard supported on HP DECwindows Motif for OpenVMS
I64 systems is the LK463 keyboard. Although other types of keyboards
may function in the OpenVMS I64 environment, HP does not currently
188.8.131.52 Connect Peripheral Devices Prior to Server Startup
To properly configure your system as a DECwindows X display server, you must have all the following peripheral components connected prior to startup:
Otherwise, the server system might not complete the device initialization process correctly. For example, starting up a server system without input devices (mouse and keyboard) could result in a blank screen.
To correct this problem, disconnect and reconnect all peripherals.
184.108.40.206 Countdown Messages Displayed During Startup
When running DECwindows Motif in client-only mode (with no server configured), messages similar to the following might be displayed during startup:
Waiting for mouse... Waiting for keyboard...
These messages indicate that device polling is underway and are informational only. They will disappear once the 15-second countdown is complete.
To prevent the messages from displaying, connect the input devices (USB
mouse and USB keyboard) to the system prior to startup.
1.9 Release Notes for OpenVMS Alpha Users
The following notes are primarily of interest to users of OpenVMS Alpha
1.9.1 Firmware for OpenVMS Alpha Version 8.2
OpenVMS Alpha Version 8.2 was tested with the platform-specific firmware included on Alpha Systems Firmware CD-ROM Version 6.8. For older platforms no longer included on the Firmware CD-ROM, OpenVMS Alpha Version 8.2 was tested with the latest released firmware version. HP recommends upgrading to the latest firmware before upgrading OpenVMS.
The OpenVMS Alpha Version 8.2 kit includes the Alpha Systems Firmware CD-ROM and Release Notes. Read the Release Notes before installing the firmware.
You can obtain Version 6.8 and the latest firmware information from the following website (URL is case sensitive):
You can upgrade directly to OpenVMS Alpha Version 8.2 from only the following versions of OpenVMS Alpha. Upgrades to OpenVMS I64 Version 8.2 are not supported.
If you are currently running OpenVMS Alpha Version 6.2x through 7.3, inclusive, you must first upgrade to Version 7.3-1 or 7.3-2, and then to Version 8.2. Note that standard support for OpenVMS Alpha Version 7.3-1 systems ends on March 31, 2005. After that, OpenVMS Alpha V7.3-1 systems will not be under Prior Version Support (PVS). For details about OpenVMS operating system support, see the chart on the following website:
If you are running other versions of OpenVMS that are no longer supported, you must do multiple upgrades in accordance with upgrade paths that were documented for earlier versions.
During a concurrent upgrade, you must shut down the entire cluster and upgrade each system disk. No one can use the cluster until you upgrade and reboot each computer. Once you reboot, each computer will be running the upgraded version of the operating system.
During a cluster rolling upgrade, you upgrade each system disk individually, allowing old and new versions of the operating system to run together in the same cluster (a mixed-version cluster). There must be more than one system disk. The systems that are not being upgraded remain available.
Only the following OpenVMS Alpha and OpenVMS VAX versions are supported in mixed-version clusters that include OpenVMS Alpha Version 8.2:
Version 7.3-2 (Alpha)
Version 7.3 (VAX)
If you are upgrading in a cluster environment, rolling upgrades are supported from Version 7.3-2 and 7.3-1 of the OpenVMS Alpha operating system. If you have other versions in a cluster, you cannot do a rolling upgrade until those versions are upgraded to a supported version.
Mixed-version support for all of these versions requires the installation of one or more remedial kits. For more information, see Section 4.18.4.
HP currently supports only two versions of OpenVMS (regardless of architecture) running in a cluster at the same time. Only two architectures are supported in the same OpenVMS Cluster. Warranted support is provided for pairings with OpenVMS I64 Version 8.2. For more information, refer to the HP OpenVMS Version 8.2 Upgrade and Installation Manual.
For a discussion of warranted pairs and migration pairs of OpenVMS
operating systems, for complete instructions for installing or
upgrading to OpenVMS Alpha Version 8.2, and for instructions on
installing OpenVMS I64 Version 8.2, refer to the HP OpenVMS Version 8.2 Upgrade and Installation Manual.
1.9.3 Error on Upgrade from Version 7.3-1
When you upgrade an OpenVMS Alpha Version 7.3-1 system disk to Alpha Version 8.2, the following error message might appear during the execution phase:
%PCSI-E-PARUDF, file [SYSLIB]SYS$STARLET_C.TLB was not previously installed or is present but out of scope; module update skipped Terminating is strongly recommended. Do you want to terminate? [YES]
This error message is not appropriate for the circumstances. It incorrectly states that the SYS$STARLET_C.TLB library cannot be updated. The cause of this problem is that a patch kit applied to the Alpha Version 7.3-1 system disk improperly updated a module in the library.
Disregard the recommendation to terminate the upgrade. Answer NO to the
Do you want to terminate? [YES]
. The upgrade will continue successfully.
1.9.4 Encryption for OpenVMS Alpha: Remove Before Upgrading
The Encryption producer name has changed from CPQ to HP for OpenVMS Alpha and Itanium systems. This name is visible in the PCSI filename and the PCSI database. For example, the following pairs demonstrate the old and new names:
CPQ AXPVMS ENCRYPT V1.6
HP AXPVMS ENCRYPT V1.6
For Alpha systems, if the ENCRYPT product was installed from an older kit (that is, a kit where HP is not listed as the Encryption producer), you must first remove ENCRYPT before you upgrade. Use the following commands:
$ PRODUCT REMOVE ENCRYPT $ PRODUCT INSTALL ENCRYPT
A license is no longer required to use the the HP Encryption product.
1.9.5 HP DECram V3.n: Remove Before Upgrading
Starting with OpenVMS Alpha and OpenVMS I64 Version 8.2, DECram ships with the OpenVMS operating system as a System Integrated Product (SIP). Before you upgrade to Version 8.2 on an OpenVMS Alpha system, you must remove any old versions of DECram. Refer to the HP OpenVMS Version 8.2 Upgrade and Installation Manual for details.
If you installed Kerberos Version 1.0 for OpenVMS using a POLYCENTER Software Installation kit, you must use the POLYCENTER Software Installation utility to remove Kerberos Version 1.0 before you upgrade the operating system. (You do not need to remove Kerberos if you are running Version 2.0 or if Version 1.0 was installed as part of the OpenVMS Version 7.3-1 operating system.)
To remove Kerberos, choose Option 6 "Remove installed products" from the installation CD main menu. During the removal, you are asked whether you want to remove the data and directories. (Data refers to the configuration data files along with the principal database, if one was created.) If you want to save this information for use later, respond "No" to the question. Return to the main menu and perform the upgrade of OpenVMS.
After the upgrade, the new Kerberos directories are located in KRB$ROOT:[*...]. (KRB$ROOT is defined as a system-wide logical name when Kerberos is started.) Kerberos data is either created during configuration or moved from the old Kerberos directories and renamed. If you removed a previously installed Kerberos kit and saved the data and directories, the data will automatically be moved into the new directories and be renamed the first time the Kerberos startup procedure is run after the upgrade.
Start the Kerberos servers by entering the following command:
Note that the Kerberos startup procedure moves and renames only known Kerberos files. Users who have created files in the old Kerberos directories must manually move those files.
For more information about installing and configuring Kerberos, refer
to HP Open Source Security for OpenVMS, Volume 3: Kerberos.
1.9.7 Converting the LANCP Device Database After Upgrading
When you upgrade to OpenVMS Alpha Version 8.2, you might also need to convert the LAN device database to the Version 8.2 format if this is not automatically done by LANACP when LANACP is first run after the upgrade.
To convert the database, issue the following LANCP commands to convert the device database and then to stop LANACP so it can be restarted to use the new database:
$ LANCP LANCP> CONVERT DEVICE_DATABASE LANCP> SET ACP/STOP LANCP> EXIT $ @SYS$STARTUP:LAN$STARTUP
When you install or upgrade to OpenVMS Alpha Version 7.3-2 or later, you must also install a new version of DECnet-Plus. One of the reasons that makes this necessary is a change of behavior in AUTOGEN (see Section 4.3).
Unlike the behavior of previous versions, DECnet-Plus for OpenVMS Version 7.3-2 and later now provides product information in NEWPARAMS.DAT records, as required by AUTOGEN. AUTOGEN anticipates this change in DECnet-Plus, so AUTOGEN does not print any warnings when it removes "bad" records from CLU$PARAMS.DAT; AUTOGEN presumes these records were made by an older DECnet-Plus kit and will be replaced by the new DECnet-Plus kit. So, under normal conditions, you will not see any striking differences in behavior during an OpenVMS Version 7.3-2 or later installation or upgrade.
However, if other products do not provide product information in NEWPARAMS.DAT records, as now required by AUTOGEN, AUTOGEN prints warning messages to both the report and the user's SYS$OUTPUT device. The warnings state that AUTOGEN cannot accept the parameter assignment found in NEWPARAMS.DAT (because no product name is attached) and that no records will be added to CLU$PARAMS.DAT. Since no records are added, the expected additions or other alterations to SYSGEN parameters will not be made, which could lead to resource exhaustion. Developers and testers of software products should be aware of this requirement; it may also be of interest to system managers.
This new behavior is intended to protect both the users and providers of layered products. By keeping this information ordered properly so that it can be updated properly, problems resulting from bad updates should be minimized.
A description of NEWPARAMS.DAT and CLU$PARAMS.DAT is included in the
AUTOGEN chapter of the HP OpenVMS System Management Utilities Reference Manual.
1.9.9 SHADOW_MAX_UNIT Default Setting and Memory Usage
OpenVMS Alpha Version 7.3 introduced minicopy support in HP Volume Shadowing for OpenVMS. As part of the minicopy functionality, a new volume shadowing system parameter, SHADOW_MAX_UNIT, was introduced. On OpenVMS Alpha systems, the default value for this system parameter is 500, which consumes 24 KB of main memory. On OpenVMS VAX systems, the default value is 100, which consumes 5 KB of main memory.
If you do not plan to use Volume Shadowing for OpenVMS, you can change the setting to its minimum of 10 (which consumes 480 bytes of main memory). By setting the default to its minimum, you free up 23.5 KB of main memory on an OpenVMS Alpha system and 4.5 KB of main memory on a VAX system.
SHAD_MAX_UNIT is a static system parameter. In order for a new setting to take effect, you must reboot your system.