J06.13 Software Installation and Upgrade Guide

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 117)
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 117)
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”.
Managing Microcode and Firmware 21