H06.16 Software Installation and Upgrade Guide

13 Loading the Previous RVU and Resuming Normal
Operations
This chapter describes how to perform a system load of the previous RVU.
NOTE: Although the H06.16 RVU supports CLIMs, earlier H-series RVUs do not. You cannot fall
back from H06.16 to an earlier H-series RVU and retain CLIM functionality, so no CLIM fallback
information is provided in this chapter.
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.)
• Under Configuration File, select Saved Version (CONFigxx.yy:). List the saved configuration
files by entering:
SCF FUP INFO $SYSTEM.ZSYSCONF.CONF*
You can refer to this listing later in the installation procedure.
• For detailed information on performing a system load, see the information about starting and
stopping a system in the NonStop Operations Guide.
CAUTION: If your intent is to remain on your current RVU, the NonStop Blade Complex
firmware must be reverted back as explained under “Revert to the Previous NonStop Blade
Complex Firmware” (page 132).
Task Overview
The procedure for loading the NonStop system on the previous RVU is:
1. Before halting the processors, modify the OSSINFIL file and migrate CLIM services and
disconnect the CLIMs.
2. Halt the processors.
3. While the processors are halted, if you are falling back to the H06.03 or H06.04 RVU, power
cycle the processors.
4. Load the system.
5. Revert firmware if necessary.
6. Install specific OSS files if necessary.
7. Verify that the system is started.
Alerts 129