J06.06 Software Installation and Upgrade Guide

13 Falling Back on the CLIMs, Loading the Previous RVU,
and Resuming Normal Operations
This chapter describes how to perform a system load of the previous RVU and how, as needed,
to revert the CLIM software and/or firmware to the previous versions.
NOTE: If your NonStop system does not have CLIMs installed, disregard the sections in this
chapter that describe CLIM fallback procedures.
Fallback Considerations for the Power Regulator
The OSM Service Connection does not support the Power Regulator feature in RVUs prior to J06.14;
therefore, falling back to an RVU prior to J06.14 always results in all server blades running in the
default Status High Performance Mode.
Alerts
Before performing a system load:
• Before halting the processors, stop running applications, including TMF.
NOTE: To stop TMF, at a TACL prompt, enter: TMFCOM STOP TMF
• Do not close the System Startup dialog box while startup is in progress. If you attempt to close
the dialog box, a message dialog box appears to alert you that the system startup process
will be stopped if you continue.
• If you stop a system startup before it has finished, the state of your system will be unpredictable.
You might need to perform another system startup to enable the system to resume normal
operation.
• If you must stop the system startup process, click Abort. (The abort process should take effect
within 30 seconds.)
• For detailed information on performing a system load, see the NonStop Operations Guide.
• List your saved configuration files by entering:
FUP INFO $SYSTEM.ZSYSCONF.CONF*
You might want to refer to this list later in the procedure.
• Check the list of fallback issues in the J06.nn Release Version Update Compendium, where
J06.nn is the RVU to which you are falling back.
Task Overview
If you have CLIMs in your system and need to fall back to the previous version of the CLIM software,
the steps to fall back on the CLIM are included in these procedures. If reverting to the previous
CLIM software is necessary or desirable, the CLIM must be reimaged, as described in these
procedures. Refer to the CLuster I/O Module (CLIM) Software Compatiblity Reference to determine
whether reverting to the previous CLIM software is necessary for your fall back scenario. If your
systems does not have CLIMs installed, you can disregard these steps.
Restoring the CLIMs assumes that you have saved the CLIM configurations by issuing the CLIMBKUP
command before upgrading your system, as described in “Back Up CLIM Configuration Files”
(page 36) and in the Cluster I/O Protocols (CIP) Configuration and Management Manual. Falling
back to previous versions of CLIM software adds approximately one hour for each CLIM to the
process of loading the system on the previous RVU.
104 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations