Installation and Upgrade Guide

Overview of Installing G06.24
G06.24 Software Installation and Upgrade Guide—528593-005
1-38
NonStop TCP/IPv6 (G06.20, G06.22, G06.23,
G06.24)
NonStop TCP/IPv6 (G06.20, G06.22, G06.23, G06.24)
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 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.
TMF (G06.23 and G06.24)
TMF Migration Considerations for SQL/MX Release 2.0
If you install SQL/MX Release 2.0, fallback and migration concerns could apply if you
have to fall back to a previous RVU. See the T8607AFH or later softdoc for detailed
migration information for TMF. See also the TMF Planning and Configuration Guide
and the TMF Operations and Recovery Guide.
If the Install SQL/MX Script has not been run on your system while running on the new
RVU, and no native-format SQL/MX metadata tables (or their resource forks) or audit
records for them have been created, there are no TMF fallback considerations.
Otherwise, you must use the appropriate DP2 (T9053) fallback SPR if you have not
performed a clean TMF shutdown.
HP strongly recommends that you successfully complete a clean TMF shutdown (with
all audited disks up) before falling back to a prior RVU. This is particularly important
whenever the RVU you are falling back from supports any new format files or objects
or audit records for them, and the fallback RVU does not.
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).