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
Threshold 86959 CPU pages
* Default swapfile extents may not be fully allocated.
Status of $SYSTEM.ZSYSSWAP.SWAP02
CPU 2
CPU Pages: Total 102305* Reserved 6361 Available 95944
Peak CPU Pages ever reserved 7280
Threshold 86959 CPU pages
* Default swapfile extents may not be fully allocated.
Status of $SYSTEM.ZSYSSWAP.SWAP03
CPU 3
CPU Pages: Total 102305* Reserved 5242 Available 97063
Peak CPU Pages ever reserved 6863
Threshold 86959 CPU pages
* Default swapfile extents may not be fully allocated..
Install Node Interoperability SPRs
Node interoperability is the ability of the nodes (systems) in an Expand network to communicate
and interact with each other. An Expand network can be interconnected using various technologies
such as Expand over IP and ServerNet Cluster. See the NonStop Networking Overview for more
information about and diagrams of NonStop platform interoperability.
In addition to interoperability issues for nodes connected through Expand, there are software
migration and software management issues to consider, such as accelerating TNS object files on
a system running an RVU series for posterior use in a system running another RVU series, DSM/SCM
software management in an environment composed of systems running different RVU series, and
moving objects built on a system running an RVU series to a system running another RVU series
by means of Expand, FTP, or media such as magnetic tapes.
NOTE: This manual does not list the SPRs needed for BladeCluster Solution interoperability. For
specific SPRs required for BladeCluster Solution, see the BladeCluster Solution Manual.
These SPRs must be installed on systems running G-series RVUs if you want the functionality it makes
available through Expand-connected H-series or J-series RVU systems.
Table 13 Interoperability SPRs for G-Series RVU Systems Connected Through Expand to H-Series
or J-Series RVU Systems
Introduced in this RVUDescriptionProduct NameMinimum SPR
G06.26Required for remote NEWPROCESS of
OCA objects*
TACLT9205D46^ACF
*T9205D46^ACF is required only if you want the functionality it provides.
These SPRs must be installed on systems running H-series RVUs for compatibility and interoperability
through a ServerNet Cluster with systems running J-Series RVUs.
Table 14 Interoperability SPRs for H-Series RVU Systems Connected through ServerNet to J-Series
RVU Systems
Introduced in this RVUDescriptionProduct NameMinimum SPR
H06.14Required for ServerNet clustering*SNETMONT0294H01^AAW
H06.14Required for ServerNet clustering*SANMANT0502H01^AAW
*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.
48 Preparing to Upgrade the Server Software (Preinstallation Tasks)