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
• As of G06.27, you can manage a J-series target system from a G-series host system. However,
you cannot currently manage a G-series target system from a J-series system.
• When you upgrade the client and server SPRs for DSM/SCM, you must also upgrade the
SWID product (T9298H02) at the same time to avoid a fingerprint or mismatched file problem.
For this RVU, SWID is already installed.
OSBUILD SPR
WARNING! If a J06.03 or later host system is used to perform DSM/SCM builds for a target
system that is running an H-series release prior to H06.12, you must include the appropriate T0431
(OSBUILD) SPR for that target system before performing the build. If this is not done, then the
DSM/SCM Sysgen (OSBUILD) will fail. The build will complete successfully if it is being done for
an H06.12 or later system.
The appropriate T0431 SPRs are:
Target NonStop System RVUSPR
H06.10 and H06.11T0431H01^AAK
H06.09T0431H01^AAH
H06.08T0431H01^AAN
H06.07T0431H01^AAM
H06.05 and H06.06T0431H01^AAL
Any J-series RVU attempting to build an H-series RVU prior to H06.12 must install these SPRs.
DSM/SCM and Public DLLs
DSM/SCM manages and controls the distribution, installation, and activation of public DLLs in
J-series RVUs the same way that it does in H-series RVUs. Public DLLs are installed on the H-series
and J-series target systems in their own subvolume.
To manage OSS files in J-series RVUs, use the T6031H01 or later SPR. The corresponding client
version, Planner Interface, or NonStop Software Essentials must also be installed. For this RVU, the
SPR for the client is T0895V02 for NonStop Essentials and T6031G02/H02 for the Planner
Interface. The DSM/SCM SPR for the server side is T6031G02/H02. The SPR for the NonStop
Software Essentials server is T90894H02 AAA and for the PI server is T6031H02.
DSM/SCM and OSS
When performing a Build/Apply, ensure that the setting of the Manage OSS Files option
matches with your target system. If the target system is not to use OSS, you must uncheck the OSS
files option box before beginning a Build request. If the box is left checked, OSS is included by
the Build request. The OSS root fileset needs to be configured and started before files can be
copied into the OSS file system by DSM/SCM. For OSS users who request HP to install OSS, it is
assumed that OSS is installed and configured. However, the OSS root fileset ($ZPNS) must be in
the started state; otherwise, the Build/Apply fails.
Upgrading the NonStop Software Essentials Client
You can now order 64-bit consoles, which require NonStop Software Essentials. (NonStop Software
Essentials is pre-installed on the 64-bit consoles. See the NonStop Software Essentials Installation
Using DSM/SCM and NonStop Software Essentials With This RVU 19