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

These specific SPRs must be installed on systems running G-series RVUs for compatibility and
interoperability through a ServerNet Cluster with systems running J-Series RVUs.
Table 15 Interoperability SPRs for G-Series RVU Systems Connected through ServerNet to J-Series
RVU Systems
Introduced in this RVUDescriptionProduct NameMinimum SPR
G06.31Required for ServerNet clustering*SNETMONT0294G08^AAX
G06.31Required for ServerNet clustering*SANMANT0502G08^AAX
G06.25Required for ServerNet clustering*OSM Service
Connection Suite
T0682G06^AAA
*For more details, see the ServerNet Cluster Supplement for HP Integrity NonStop BladeSystems. To find out if your
NonStop server supports ServerNet clustering, see the planning guide for your NonStop server.
These SPRs must be installed on systems running G-Series RVUs for compatibility and interoperability
through a ServerNet Cluster with systems running H-Series RVUs.
Table 16 Interoperability SPRs for G-Series RVU Systems Connected through ServerNet to H-Series
RVU Systems
Introduced in this RVUDescriptionProduct NameMinimum SPR
G06.26Required for ServerNet clustering*SNETMONT0294G08^AAP
G06.26Required for ServerNet clustering*SANMANT0502G08^AAN
G06.25Required for ServerNet clustering*OSM Service
Connection Suite
T0682G06^AAA
*For more details, see the ServerNet Cluster Supplement for NonStop NS-Series Servers. To find out if your NonStop
server supports ServerNet clustering, see the planning guide for your NonStop server.
These SPRs facilitate software migration and software management operations between nodes
running G-series RVUs and nodes running H-series and J-series RVUs:
• The T9621D30^ABB, T9674D30^AAM, T9276D30^AAW, and T0448G06^AAA SPRs
provide the option of using a G-series RVU system to construct objects that will ultimately run
on an H-series or J-series RVU system. Possible activities that can be performed in the G-series
RVU system include accelerating objects that will eventually run on an H-Series or J-series RVU
system. Once the objects have been properly constructed on the G-series RVU system, they
can be moved to the H-Series or J-series RVU system by whatever means preferred, for example,
by Expand, FTP, or magnetic tape. For more details, please refer to the H-Series Application
Migration Guide.
• T6031G01^ABP provides the option to use DSM/SCM to manage software in an environment
composed of systems running different RVU series. The systems need not be connected through
Expand.
• T9617G03^AAY allows you to check the VPROC of H-series and J-Series object files that
have been copied to a G-series RVU system or in situations where a G-series RVU node is
used to manage software for a H-series or J-series RVU system. This functionality can also be
used to query the VPROC of a remote object file through Expand.
Table 17 SPRs for Software Migration and Software Management Operations Between G-Series,
H-Series and J-Series RVU-Based Systems
Introduced in this RVUDescriptionProduct NameMinimum SPR
G06.27Required to recognize 800 filesVPROCT9617G03^AAY
G06.27Required to recognize OCA regionBinderT9621D30^ABB
Install Node Interoperability SPRs 49