G06.32 Software Installation and Upgrade Guide

G06.32 Installation and Fallback Alerts

G06.32 Software Installation and Upgrade Guide—546068-002

2-27

System Configuration Database

To ensure system configuration integrity, always save the current system configuration

database (CONFIG) before installing software or making changes to your system

configuration. You must load the G06.32 operating system before making changes to

the configuration database.

For information on saving the current system configuration database, see Save the

Current Configuration File (CONFxxyy) on page 5-1.

NonStop TCP/IPv6

With the introduction of HP NonStop TCP/IPv6 in the G06.20 RVU, all NonStop

TCP/IPv6 protocol files are located in $SYSTEM.ZTCPIP subvolume. If you are

upgrading from a pre-G06.20 RVU, back up your HP NonStop TCP/IP configuration

files

before

running ZPHIRNM. (HP recommends backing up your TCP/IP configuration

files before running ZPHIRNM even if you are on a G06.20 or later RVU.) If you have

to restore information on network services and connections, you will need these files

for the proper network information.

When resuming normal operations after a system load has been performed, you must

have all NonStop TCP/IP configuration files in your $SYSTEM.ZTCPIP subvolume.

Otherwise, applications dependent on proper network connections will fail.

For complete installation instructions, see Back Up (Copy) Files in the

$SYSTEM.ZTCPIP Subvolume on page 11-2 and Update TCP/IP Configuration Files

on page 13-1.

TMF

TMF 3.3 Fallback Issues

Beginning with G06.26, if you do not use any new configurable features after migrating

to TMF 3.3, falling back to the RVU from which you migrated is not a problem. If you

use certain new TMF 3.3 features, however, it is important to first understand how that

impacts subsequent fallback:

Caution. Starting with the G06.06 RVU, the configuration file is automatically upgraded to alter

records for all storage devices. Loading the system with an upgraded configuration file and a

previous RVU causes a processor halt (disk-process error code%011500).

Note.

•

For the DSM/SCM Planner Interface to be operational, the PORTCONF file must have the

correct entry for DSM/SCM. The SERVICES file must have an entry that specifies DSM

and its corresponding port number.

•

Keep your current PROTOCOL file in your $SYSTEM.ZTCPIP subvolume. Update it with

the new lines from the sample PROTOCOL file (SMPLPROT).