J06.15 Software Installation and Upgrade Guide

STANDARD_MICROCODE TANDEM^STANDARD^MICROCODE;
MICROCODE_FILES TANDEM^MICROCODE^FILES;
FILES_TO_COPY_TO_NEW_SYSTEM TANDEM^FILES^TO^COPY;
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;
FORMATTER_TEMPLATE_FILES TANDEM^FORMATTER^TEMPLATE^FILES;
INITIAL_COMINT_INFILE $DSMSCM.SYS.CIIN;
Installing CLIM Software
If your NonStop system has CLIMs installed, you must upgrade the CLIM software prior to cold
loading the SUT. The procedure for upgrading CLIM software is described in the Cluster I/O
Protocols (CIP) Configuration and Management Manual.
Backing Out the DSM/SCM Revision
If you encounter a problem with a SUT refresh that cannot be resolved, you can back out the
DSM/SCM revision.
Table 1 Tasks and Tools for Backing Out to the Previous SYSnn
Documented in This Chapter...Use This Tool...To Perform This Task...
“Backing Out the DSM/SCM Revision ”
(page 20)
DSM/SCM Target Interface (ZPHITI)1. Submit a backout request.
Chapter 12: “Running ZPHIRNM to
Reactivate the Previous Software
Revision”
DSM/SCM ZPHIRNM program2. Reactivate the previous software
revision.
“Falling Back on the CLIMs, Loading the
Previous RVU, and Resuming Normal
Operations ” (page 118)
OSM Low-Level Link3. Load the HP NonStop operating
system and, if CLIMs are installed,
load the CLIM software from the
previous revision into the first
processor.
“Falling Back on the CLIMs, Loading the
Previous RVU, and Resuming Normal
Operations ” (page 118)
TACL RELOAD command4. Reload the remaining processors.
Managing Microcode and Firmware
When you install a new RVU, you must ensure you are running the current firmware and microcode
versions and upgrade those products, if necessary. The current firmware versions and upgrade
procedures are given in Chapter 2: “Managing Microcode and Firmware”
Installation, Migration, and Fallback
Many products have special considerations for installation, migration, and fallback, which you
should be aware of before installing the new RVU. These considerations are described in Chapter 3:
“Installation, Migration, and Fallback Considerations for This RVU”.
Perform an RVU Upgrade on a Node
For instructions on how to perform an RVU upgrade on a node connected to any ServerNet Cluster
topology (such as a BladeCluster Solution, ServerNet Cluster 6770, ServerNet Cluster 6780, or
a combination of these topologies), see the procedure in the NonStop BladeCluster Solution Manual.
20 Overview of Installing This RVU