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

request is finished, a snapshot is automatically created and returned to the host, if
Expand-connected.
4. Activate the new operating system image.
During the Build/Apply phase, DSM/SCM places product files in their TSVs with temporary
(fabricated) file names so that the new files do not conflict with the file names of currently
running programs. You run the ZPHIRNM program on the target system to:
• Rename the files that currently have actual file names to fabricated names. These files
become obsolete when the new files are renamed.
• Rename the new files, which have fabricated names, to their actual names.
After ZPHIRNM has completed renaming all OSS and Guardian files, it will run ZMODGP
if it exists in the SYSnn being activated and if:
◦ The configuration being activated contains a ZCNFDEFS TSV
◦ One or more of the ZcccGP files in the ZCNFDEFS TSV are new or changed (as
compared to the last configuration activated).
If no ZcccGP files change, ZMODGP is not run.
ZMODGP is a TACL script that makes changes to the generic-process definitions in
the system configuration database. When you use the ZMODGP script, you do not
need to hard code new generic process definitions directly into the $ZCDB process
(T6586, Configuration Services).
Check or Alter the CONFTEXT File Before Installing This RVU SUT
NOTE: Tape_Label_Processing is controlled by the Storage Subsystem ($ZZSTO) ALTER SUBSYS
command. The CONFTEXT file directive TAPE_LABEL_PROCESSING gets overridden by the Storage
Subsystem settings. See the SCF Reference Manual for the Storage Subsystem for more information
about the ALTER SUBSYS command.
The processor type (SYSTEM_PROCESSOR_TYPE) is specified in the CONFTEXT file. It currently
has only one value:
SYSTEM_PROCESSOR_TYPESystem
NSE-MNB50000c, NB50000c-cg,
NB54000c, NB54000c-cg, NS2200
series, and NS2000 Series
Check the CONFTEXT file to ensure that the following entries are present. They are needed for the
implicit DLLs:
SYSTEM_IMPLICIT_INIT_FILES TANDEM^IMPLICIT^INIT^FILES;
SYSTEM_IMPLICIT_CORE_FILES TANDEM^IMPLICIT^CORE^FILES;
SYSTEM_IMPLICIT_FS_FILES TANDEM^IMPLICIT^FS^FILES;
SYSTEM_IMPLICIT_MCP_FILES TANDEM^IMPLICIT^MCP^FILES;
SYSTEM_IMPLICIT_ETC_FILES TANDEM^IMPLICIT^ETC^FILES;
This example shows a CONFTEXT file:
$TEMP CONFIGXX 2> type conftext
ALLPROCESSORS:
SYSTEM_PROCESSOR_TYPE NSE-M;
SYSTEM_VOLUME_SUBVOL $SYSTEM.SYS00;
SYSTEM_LIBRARY_CODE_FILES TANDEM^LIBRARY^CODE^FILES;
SYSTEM_PROCESS_CODE_FILES TANDEM^PROCESS^CODE^FILES;
SYSTEM_PROCESS_LIBRARY_FILES TANDEM^PROCESS^LIBRARY^FILES;
Using DSM/SCM and NonStop Software Essentials With This RVU 21