G06.27 Software Installation and Upgrade Guide

Overview of Installing G06.27
G06.27 Software Installation and Upgrade Guide—540067-001
1-42
System Configuration Database
See the SCF Reference Manual for the Kernel Subsystem for details on these SCF
attributes.
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.27 operating system before making changes to
the configuration database.
See Save the Current Configuration File (CONFxxyy) on page 4-1 for information on
saving the current system configuration database.
NonStop TCP/IPv6 (G06.20 through G06.26)
With the introduction of 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 the 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 10-2 and Update TCP/IP Configuration Files
on page 12-1.
Note. Note that these three attributes are maintained system-wide; the settings affect all
processors in the node. The misalignment events (if any) are viewed by using existing EMS
event viewers (for example, Viewpoint, TSM, and OSM). The EMS subsystem identifier is
GUARDLIB, and the event number is 108. For information on how to check EMS logs, see the
EMS Manual.
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).