J06.08 Software Installation and Upgrade Guide
Table Of Contents
- J06.08 Software Installation and Upgrade Guide
- Contents
- About This Document
- 1 Overview of Installing This RVU
- SUT on DVD
- CLIM Software for This RVU
- Disk Space Requirements
- Operational Differences Between This RVU and H-series RVUs
- Investigating a J-Series RVU
- System Console Requirements
- Using OSM With This RVU
- Using DSM/SCM and NonStop Software Essentials With This RVU
- NonStop Software Essentials and This RVU
- DSM/SCM and This RVU
- DSM/SCM and Public DLLs
- DSM/SCM and OSS
- Upgrading the NonStop Software Essentials Client
- Upgrading the DSM/SCM Client (Planner Interface) and the T6031H02 PVU
- Summary of Software Installation Tasks
- Check or Alter the CONFTEXT File Before Installing This RVU SUT
- Installing CLIM Software
- Backing Out the DSM/SCM Revision
- Managing Microcode and Firmware
- Installation, Migration, and Fallback
- 2 Managing Microcode and Firmware
- Managing ME Firmware and ME FPGA Firmware
- Managing OA Firmware for the c7000 Enclosure
- Managing Server Blade Firmware
- Managing ServerNet Adapter Firmware
- Managing SWAN and SWAN 2 Concentrator Firmware
- Managing NonStop Cluster Switch Firmware
- Managing CLIM Firmware
- Managing S-Series Interoperability Firmware
- 3 Installation, Migration, and Fallback Considerations for This RVU
- 4 Upgrade Checklist
- 5 Preparing to Upgrade the Server Software (Preinstallation Tasks)
- Back Up Important Files
- Record the Current SYSnn
- Save the Current Configuration File (CONFxxyy)
- Verify System Processes
- Check Processor Status
- Check System Components
- Verify the State of the Internal ServerNet Fabric
- Verify Firmware
- Verify Critical System Processes
- Verify Disk Drives
- Verify Tape Drives (If Necessary)
- Verify That the CLIMs Are in the Started State
- Verify That the CIP Providers Are in the Started State
- Check the Status of the Spooler Collector
- Check for Sufficient Swap File Space
- Install Node Interoperability SPRs
- Back Up System Information
- Manually Install the NonStop Software Essentials Server Product
- 6 Installing a SUT for This RVU Using NonStop Software Essentials
- 7 Installing a SUT for This RVU Using the Planner Interface
- 8 Running ZPHIRNM
- 9 Loading This RVU
- 10 Resuming Normal Operations
- Revive the Down Half of the Mirrored Disk
- Validate Your Core License
- Start System Applications
- Run merge_whatis
- Configure Specific Products (Post-System Load)
- 11 Backing Out the DSM/SCM Revision
- 12 Running ZPHIRNM to Reactivate the Previous Software Revision
- 13 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations
- Fallback Considerations for the Power Regulator
- Alerts
- Task Overview
- Before Halting the Processors
- Halt the Processors
- While the Processors are Halted
- Prepare the CLIMs
- Load the System
- Complete CLIM Setup
- Revert Firmware (If Necessary)
- Install Specific OSS Files (If Necessary)
- Verify That the System Is Started
- A Using DSM/SCM and NonStop Software Essentials to Install SPRs
- B Using DSM/SCM and Planner Interface to Install SPRs
- C Installing SWID and DSM/SCM PVU Using NonStop Software Essentials Client Software
- Alerts
- Copy (RESTORE) the H02 DSM/SCM Product Version to Disk (If Necessary)
- Receive the H02 SWID and DSM/SCM SPRs
- Create a New Software Revision for H02 DSM/SCM and SWID SPRs
- Build and Apply the DSM/SCM H02 Software Product Revision
- Run the INSTALL^TEMPLATES Macro
- Restart Applications
- Recovery for Problems While Installing the H02 Version of DSM/SCM
- Install the NonStop Software Essentials Client
- Install the NonStop Essentials Client From the HP Insight Control for NonStop DVD
- D Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software
- Alerts
- Copy (RESTORE) the H02 DSM/SCM Product Version to Disk (If Necessary)
- Receive the H02 SWID and DSM/SCM SPRs
- Create a New Software Revision for H02 DSM/SCM and SWID SPRs
- Build and Apply the DSM/SCM H02 Software Product Revision
- Rename the Applied DSM/SCM H02 Files By Running ZPHIRNM
- Run the INSTALL^TEMPLATES Macro
- Restart Applications
- Recovery for Problems While Installing the H02 Version of DSM/SCM
- Install the DSM/SCM Client From ZDSMSCM
- E Updating SWAN Concentrator CLIP Firmware
- Acronyms
- Index
3 Installation, Migration, and Fallback Considerations for
This RVU
See the Readme file and the appropriate softdocs for the latest information on any migration or
configuration steps. Considerations in this chapter are categorized according to the RVU at which
they were introduced.
J06.04
Compiling C++ Programs to Run on RVUs Earlier Than J06.04
Objects compiled by the J06.04 and later C++ compilers might require new functions that are in
the current C++ Common Runtime Library but not in RVUs earlier than J06.04. Specifically, programs
that use either of the following features will fail to load because of unresolved externals (assuming
that they are not linked using the –rld_unresolved ignore option):
• A try catch block
• An exception specifier
To ensure that these programs run correctly on RVUs earlier than J06.04, you must specify the
-WRVU=H06.nn parameter on the c89 command (OSS or PC environment), or the RVU=H06.nn
parameter on the CPPCOMP command (Guardian environment), where nn indicates the RVU on
which the objects will run.
NOTE: The RVU and -WRVU command line parameters do not support J-series RVUs. If J06.03
is the intended target system, specify H06.14.
NOTE: If you are compiling for an H-series target system, nn must be between 08 and 14,
inclusive, as the Runtime Library supports only RVUs H06.08 and later.
You can fix the problem by installing T2831H01^AAD (Common Runtime Library) or later on all
target systems that will run programs generated by the J06.04 or later version of the C++ compiler.
NOTE: You must reboot the system after installing T2831H01^AAD.
SQL/MX Versioning Feature Removed
Certain SQL/MX versioning enhancements that were introduced in an earlier H-series RVU have
been removed in the J06.04 and later RVUs. The following enhancements are no longer supported:
• Ability of Expand-connected nodes with compatible SQL/MX versions to interoperate.
• Predictable failure on access to or from nodes with incompatible SQL/MX versions.
• Ability of each version of SQL/MX to determine compatibility.
CLIM
The CLIM is introduced in the J06.04 RVU. CLIM is a rack-mounted HP ProLiant class server that
provides connectivity between the NonStop host system and either the network or the storage
devices. For CLIM upgrade procedures, see the Cluster I/O Protocols (CIP) Configuration and
Management Manual. For fallback procedures, see Chapter 13.
CLIMs with software associated with J06.04 are not compatible with RVUs of J06.06 and later
RVUs. However, if you are migrating from a J06.04 RVU to a J06.06 or later RVU, the software
upgrade procedures in this manual are ordered so that the CLIM and RVU compatibility is assured
because the RVU on the host is updated first, then, while the processors are halted, the CLIMs are
updated to the CLIM software version associated with this RVU. When the system is loaded, the
CLIM and the NonStop host are at the same level and are therefore compatible.
J06.04 31