J06.08 Software Installation and Upgrade Guide
Table Of Contents
- J06.08 Software Installation and Upgrade Guide
- Contents
- About This Document
- 1 Overview of Installing This RVU
- SUT on DVD
- CLIM Software for This RVU
- Disk Space Requirements
- Operational Differences Between This RVU and H-series RVUs
- Investigating a J-Series RVU
- System Console Requirements
- Using OSM With This RVU
- Using DSM/SCM and NonStop Software Essentials With This RVU
- NonStop Software Essentials and This RVU
- DSM/SCM and This RVU
- DSM/SCM and Public DLLs
- DSM/SCM and OSS
- Upgrading the NonStop Software Essentials Client
- Upgrading the DSM/SCM Client (Planner Interface) and the T6031H02 PVU
- Summary of Software Installation Tasks
- Check or Alter the CONFTEXT File Before Installing This RVU SUT
- Installing CLIM Software
- Backing Out the DSM/SCM Revision
- Managing Microcode and Firmware
- Installation, Migration, and Fallback
- 2 Managing Microcode and Firmware
- Managing ME Firmware and ME FPGA Firmware
- Managing OA Firmware for the c7000 Enclosure
- Managing Server Blade Firmware
- Managing ServerNet Adapter Firmware
- Managing SWAN and SWAN 2 Concentrator Firmware
- Managing NonStop Cluster Switch Firmware
- Managing CLIM Firmware
- Managing S-Series Interoperability Firmware
- 3 Installation, Migration, and Fallback Considerations for This RVU
- 4 Upgrade Checklist
- 5 Preparing to Upgrade the Server Software (Preinstallation Tasks)
- Back Up Important Files
- Record the Current SYSnn
- Save the Current Configuration File (CONFxxyy)
- Verify System Processes
- Check Processor Status
- Check System Components
- Verify the State of the Internal ServerNet Fabric
- Verify Firmware
- Verify Critical System Processes
- Verify Disk Drives
- Verify Tape Drives (If Necessary)
- Verify That the CLIMs Are in the Started State
- Verify That the CIP Providers Are in the Started State
- Check the Status of the Spooler Collector
- Check for Sufficient Swap File Space
- Install Node Interoperability SPRs
- Back Up System Information
- Manually Install the NonStop Software Essentials Server Product
- 6 Installing a SUT for This RVU Using NonStop Software Essentials
- 7 Installing a SUT for This RVU Using the Planner Interface
- 8 Running ZPHIRNM
- 9 Loading This RVU
- 10 Resuming Normal Operations
- Revive the Down Half of the Mirrored Disk
- Validate Your Core License
- Start System Applications
- Run merge_whatis
- Configure Specific Products (Post-System Load)
- 11 Backing Out the DSM/SCM Revision
- 12 Running ZPHIRNM to Reactivate the Previous Software Revision
- 13 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations
- Fallback Considerations for the Power Regulator
- Alerts
- Task Overview
- Before Halting the Processors
- Halt the Processors
- While the Processors are Halted
- Prepare the CLIMs
- Load the System
- Complete CLIM Setup
- Revert Firmware (If Necessary)
- Install Specific OSS Files (If Necessary)
- Verify That the System Is Started
- A Using DSM/SCM and NonStop Software Essentials to Install SPRs
- B Using DSM/SCM and Planner Interface to Install SPRs
- C Installing SWID and DSM/SCM PVU Using NonStop Software Essentials Client Software
- Alerts
- Copy (RESTORE) the H02 DSM/SCM Product Version to Disk (If Necessary)
- Receive the H02 SWID and DSM/SCM SPRs
- Create a New Software Revision for H02 DSM/SCM and SWID SPRs
- Build and Apply the DSM/SCM H02 Software Product Revision
- Run the INSTALL^TEMPLATES Macro
- Restart Applications
- Recovery for Problems While Installing the H02 Version of DSM/SCM
- Install the NonStop Software Essentials Client
- Install the NonStop Essentials Client From the HP Insight Control for NonStop DVD
- D Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software
- Alerts
- Copy (RESTORE) the H02 DSM/SCM Product Version to Disk (If Necessary)
- Receive the H02 SWID and DSM/SCM SPRs
- Create a New Software Revision for H02 DSM/SCM and SWID SPRs
- Build and Apply the DSM/SCM H02 Software Product Revision
- Rename the Applied DSM/SCM H02 Files By Running ZPHIRNM
- Run the INSTALL^TEMPLATES Macro
- Restart Applications
- Recovery for Problems While Installing the H02 Version of DSM/SCM
- Install the DSM/SCM Client From ZDSMSCM
- E Updating SWAN Concentrator CLIP Firmware
- Acronyms
- Index
>FUP DUP $SYSTEM.ZTCPIP.SMPLPORT, $SYSTEM.ZTCPIP.PORTCONF
>FUP DUP $SYSTEM.ZTCPIP.SMPLRESC, $SYSTEM.ZTCPIP.RESCONF
>FUP DUP $SYSTEM.ZTCPIP.SMPLSERV, $SYSTEM.ZTCPIP.SERVICES
Step 2: Check the PROTOCOL File (Optional)
CAUTION: For both CIP and NonStop TCP/IPv6 (even if running in IPv4 mode), you must make
sure that the PROTOCOL file contains ipv6 and icmpv6 entries. If these entries are absent, a network
failure might occur because the new socket routines present in TELSERV, LISTNER, and FTP access
the entries in the PROTOCOL file.
If the PROTOCOL configuration file exists in $SYSTEM.ZTCPIP, you must add two lines from the
sample PROTOCOL file (SMPLPROT). Find the lines in SMPLPROT from the SUT that refer to IPV6
and ICMPV6 and copy those lines into your $SYSTEM.ZTCPIP.PROTOCOL file. For example:
12> TYPE SMPLPROT
#
# @(#)protocols 1.1 Tandem
#
# Internet (IP) protocols
# This file is never consulted when the yellow pages are running
#
ip 0 IP # internet protocol, pseudo protocol number
icmp 1 ICMP internet control message protocol
ggp 3 GGP gateway-gateway protocol
tcp 6 TCP transmission control protocol
pup 12 PUP PARC universal packet protocol
udp 17 UDP user datagram protocol
ipv6 41 IP internet protocol for v6
icmpv6 58 ICMP internet control message protocol for v6
Step 3: Optional: For Planner Interface, Ensure That PORTCONF and SERVICES Files Are Complete
The PORTCONF file specifies the ports that the LISTNER process listens to and the corresponding
server program it invokes when the request comes in.
If you copied files as documented in Step 1, for the DSM/SCM Planner Interface to work, you must
add a services line corresponding to DSM/SCM in the PORTCONF file (shown in bold lettering)
and save the file. If you did not copy the files as documented in Step 1, no action is necessary.
An example of the PORTCONF file:
58> type portconf
#
# This file tells the listner program which ports to
# listen to, and what programs to run
# Telnet is directly, and does not use the listner's
# services.
# To run the listner use:
# $system.ztcpip.listner / name.../ [config-file-name]
# where config-file-name is this file.
#
ftp $system.ztcpip.ftpserv
finger $system.ztcpip.fingserv
7 $system.ztcpip.echoserv
phiwsock $dsmscm.zdsmscm.pdpexe
Applications use the SERVICES file to retrieve the service port numbers and service names. If you
copied files as documented in Step 1, check that the last lines of the SERVICES file have an entry
similar to:
96 Resuming Normal Operations