J06.14 Software Installation and Upgrade Guide

ManualsBrandsHP ManualsServerHP Integrity NonStop Release and Migration

J06.14 Software Installation and Upgrade

Guide

HP Part Number: 696596-002

Published: March 2014

Edition: J06.14 RVU

Summary of content (168 pages)

PAGE 1
J06.14 Software Installation and Upgrade Guide HP Part Number: 696596-002 Published: March 2014 Edition: J06.
PAGE 2
© Copyright 2012, 2014 Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
PAGE 3
Contents About This Document...................................................................................11 Supported RVUs.....................................................................................................................11 Intended Audience..................................................................................................................11 New and Changed Information in This Edition............................................................................
PAGE 4
Compiling C++ Programs to Run on RVUs Earlier Than J06.04.................................................30 SQL/MX Versioning Feature Removed..................................................................................30 CLIM................................................................................................................................30 J06.05..................................................................................................................................
PAGE 5
Preparing to Upgrade the Server Software (Preinstallation Tasks).....................44 Back Up Important Files...........................................................................................................44 Back Up NonStop SQL/MP.................................................................................................44 Back Up NonStop SQL/MX files..........................................................................................44 Back Up Spooler Control files.................
PAGE 6
Verify That ZPHIRNM Ran Successfully..................................................................................88 9 Loading This RVU.....................................................................................89 Alerts....................................................................................................................................91 Perform Updates.....................................................................................................................91 1.
PAGE 7
Open System Services......................................................................................................108 Storage Management Foundation .....................................................................................108 Before Backing Out the Revision.............................................................................................108 Start the Target Interface (ZPHITI)............................................................................................
PAGE 8
If a System Load Is Required...................................................................................................136 Halt the Processors ..........................................................................................................136 Perform a System Load......................................................................................................137 Start Your Applications and Processes.................................................................................
PAGE 9
Determine the Product Version of DSM/SCM on the Host System and SUT...............................153 Determine the SWID Product Version on the Host System and SUT..........................................153 Determine the Product Version of DSM/SCM on the Client....................................................153 Copy (RESTORE) the H02 DSM/SCM Product Version to Disk (If Necessary).................................154 Receive the H02 SWID and DSM/SCM SPRs .................................................
PAGE 10
Tables 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Tasks and Tools for Backing Out to the Previous SYSnn .........................................................20 Maintenance Entity (ME) Firmware File Names and Locations................................................22 Maintenance Entity (ME) FPGA File Names and Locations.....................................................23 Server Blade Firmware for All NonStop System Running J-Series Software Except for the NS2000 Series System................
PAGE 11
About This Document This guide describes: • Upgrading the initial J06.14 RVU through the use of SUT refreshes, if necessary. • Falling back to a previous SYSnn. Supported RVUs This manual supports the J06.14.00 RVU and all subsequent J06.14.nn RVUs unless otherwise noted.
PAGE 12
Notation Conventions General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH Italic Letters Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed in brackets are required.
PAGE 13
• The Support and Service library and guided procedures provide online help and web-based instructions for performing many tasks, including updating firmware. The Support and Service library is available in the NonStop Technical Library (NTL). • The NonStop Software Essentials User's Guide provides detailed, task-oriented instructions for using NonStop Software Essentials.
PAGE 14
1 Overview of Installing This RVU For information on installing SPRs, see “Using DSM/SCM With NonStop Software Essentials to Install SPRs” (page 131) or “Using DSM/SCM With the Planner Interface to Install SPRs” (page 138). SUT on DVD The J-series SUT is also available on DVD. For instructions on installing the SUT from the DVD, see the IPSetup User’s Guide.
PAGE 15
Online help for using Scout is available on the Scout Web site. • Scout or the DSM/SCM Planner Interface can be used to view and print softdocs and release documents on the SUT after you receive new software into the archive. For more information, see the DSM/SCM User's Guide or Scout. System Console Requirements A NonStop system console (NSC) is an HP-supplied personal computer used to run OSM and other maintenance and diagnostic software for NonStop servers.
PAGE 16
Using OSM With This RVU OSM Server-Based Component The server-based OSM SPR released with this RVU is T0682H02^ACZ. This version may be superseded by a later version. For highlights of this server version, see the J06.14 Release Version Update Compendium or the OSM Service Connection User’s Guide, which is also available as online help with the OSM Service Connection. For detailed information about the OSM server-based component, including configuration options, see the OSM Configuration Guide.
PAGE 17
DSM/SCM and This RVU CAUTION: Before you install the SUT, you must copy the SUT versions of the DSM/SCM server and client products to your host system. When you copy the server and client SPRs for DSM/SCM, you must also upgrade the SWID product (T9298H02) at the same time to avoid a fingerprint or mismatched file problem.
PAGE 18
DSM/SCM and OSS When performing a Build/Apply, ensure that the setting of the Manage OSS Files option matches your target system. If the target system is not to use OSS, you must uncheck the OSS files option box before beginning a Build request. If the box is left checked, OSS is included by the Build request. The OSS root fileset needs to be configured and started before files can be copied into the OSS file system by DSM/SCM.
PAGE 19
request is finished, a snapshot is automatically created and returned to the host, if Expand-connected. 4. Activate the new operating system image. During the Build/Apply phase, DSM/SCM places product files in their TSVs with temporary (fabricated) file names so that the new files do not conflict with the file names of currently running programs. You run the ZPHIRNM program on the target system to: • Rename the files that currently have actual file names to fabricated names.
PAGE 20
STANDARD_MICROCODE MICROCODE_FILES FILES_TO_COPY_TO_NEW_SYSTEM SYSTEM_IMPLICIT_INIT_FILES SYSTEM_IMPLICIT_CORE_FILES SYSTEM_IMPLICIT_FS_FILES SYSTEM_IMPLICIT_MCP_FILES SYSTEM_IMPLICIT_ETC_FILES FORMATTER_TEMPLATE_FILES INITIAL_COMINT_INFILE TANDEM^STANDARD^MICROCODE; TANDEM^MICROCODE^FILES; TANDEM^FILES^TO^COPY; TANDEM^IMPLICIT^INIT^FILES; TANDEM^IMPLICIT^CORE^FILES; TANDEM^IMPLICIT^FS^FILES; TANDEM^IMPLICIT^MCP^FILES; TANDEM^IMPLICIT^ETC^FILES; TANDEM^FORMATTER^TEMPLATE^FILES; $DSMSCM.SYS.
PAGE 21
2 Managing Microcode and Firmware NOTE: Trained HP authorized service providers will update the firmware when they install any FRUs. Firmware, unless otherwise noted, is considered customer-updateable. You must manage all microcode and firmware within your system properly, ensuring compatible versions are installed. Failure to do so can result in a wide range of system problems, from intermittent faults to partial or complete system outages.
PAGE 22
Table 2 Maintenance Entity (ME) Firmware File Names and Locations Firmware Name Component File Name Default Location ME firmware (see Caution below) ServerNet Switch (IOAM enclosure) M2805 SYSnn subvolume Blade ME firmware (see Caution below) ServerNet Switch (c7000 enclosure) M4805 SYSnn subvolume M1805 SYSnn subvolume ME firmware for IME in VIO enclosure logic board G16SE and VIO enclosures (see Caution below) For more information on managing ME firmware, see: • The planning guide or hardw
PAGE 23
NOTE: In the OSM Low-Level Link, a G16SE enclosure is shown as a VIO module. In the OSM Low-Level Link, a VIO or G16SE logic board is represented as an IME object. To use the OSM Service Connection to update the ME firmware for VIO and G16SE enclosures: 1. Locate the VIO Logic Board: in the tree pane, select one of, depending on the type of server: • System > Fabric Group > Internal ServerNet Fabric > VIO Module > VIO Logic Board. or • 2. 3. 4. 5.
PAGE 24
Table 4 Server Blade Firmware for All NonStop System Running J-Series Software Except for the NS2000 Series System Firmware Name Product Description Halted State Services firmware Used to reset, halt, load, and dump a server blade. Delivered as an Independent Product on the NSC DVD. ISP1040 firmware Controller firmware for legacy I/O or SCSI disks in G-series RVUs. DISKBOOT firmware Used during a system load.
PAGE 25
For detailed information on updating FCSA, G4SA, and CCSA firmware using the OSM Service Connection, see the OSM online help on the OSM Multi-Resource Action dialog box. • FCSA. The FCSA has two ports that allow connection to external fibre-channel-enabled devices. The firmware files are preinstalled on the FCSAs in a new NonStop BladeSystem. You might need to update these firmware files using either OSM or SCF.
PAGE 26
• • 26 G4SA. G4SAs can only be installed in an IOAM. Firmware is preinstalled on G4SAs in a new NonStop BladeSystem. You might need to update the firmware using either OSM or SCF. ◦ Use the OSM Service Connection to display G4SA firmware attributes and action under the G4SA SAC object. To check or update G4SA firmware using the OSM Service Connection, locate and expand the G4SA, then select its subcomponent G4SA SAC object.
PAGE 27
• ◦ If the CCSA firmware attributes show that the current firmware Version is the same as the available Default File Version; no update is necessary. If the Compare State was Down-rev, you would use the Firmware Update action to update the firmware. ◦ For more information about the CCSA, refer to the LAN Configuration and Management Manual. See also “Managing S-Series Interoperability Firmware” (page 28) and the NonStop Firmware Matrices. TRSA.
PAGE 28
Table 8 Updateable Firmware for the NonStop ServerNet 6770 and 6780 Cluster Switch File Names and Locations Firmware Name Component File Name Router-2 ASIC* firmware 6780 Cluster M2789 Switch logic board SYSnn subvolume SCF or OSM Service Connection ServerNet Cluster 6780 Operations Guide Switch configuration firmware 6770 Cluster Switch SYSnn subvolume SCF or OSM Service Connection ServerNet Cluster 6770 Hardware Installation and Support Guide M6770 Default Location Tool Managing CLIM Firmwar
PAGE 29
Table 9 Updateable Firmware for S-series Interoperability.
PAGE 30
3 Installation, Migration, and Fallback Considerations for This RVU See the Readme file and the appropriate softdocs for the latest information on any migration or configuration steps. Considerations in this chapter are categorized according to the RVU at which they were introduced. J06.04 Compiling C++ Programs to Run on RVUs Earlier Than J06.04 Objects compiled by the J06.
PAGE 31
If the CLIM is in the STARTED state, you can determine the CLIM software version by using OSM Low-Level Link, OSM Service Connection or by entering: SCF-> VERSION CLIM $ZZCIP.clim-name If the CLIM is not in the STARTED state, you can use the CLIMCMD command with the Linux cat subcommand by entering: TACL>climcmd clim-name cat /etc/vproc Multiple versions of CLIM software are allowed on a system as long as all CLIMs have CLIM SPRs that are compatible with the host RVU.
PAGE 32
Falling Back to An Earlier Version of AF_UNIX If fallback is required: • If you start $ZPLS in a startup script using the SCF START SERVER command, modify startup scripts to start $ZPLS using the SCF START SERVER command. • If you use the STARTOSS utility to start OSS processes, modify the target-volume.ZOSSINS.OSSINFIL file by changing the line * SERVER #ZPLS to SERVER #ZPLS NOTE: target-volume is normally $SYSTEM. This ensures that the OSS Socket Local Server is started correctly as system load.
PAGE 33
J06.06 CLuster I/O Module (CLIM) Software Compatibility For J06.06 and subsequent J-series RVUs, CLIM software associated with the RVU is compatible with the current RVU and all preceding RVUs (J06.06 and above). NOTE: The NonStop host RVU is not compatible with every CLIM version. The CLIM must be at the NonStop host RVU version or above. Therefore, when you upgrade your NonStop host RVU, you must also update your CLIM to the software level associated with the RVU to which you are upgrading.
PAGE 34
DSM/SCM Upgrade Issues/Interoperability SPR Requirements If you are migrating from a J06.04 or earlier RVU to a J06.07 or later RVU, be aware that the USERID attributes of all persistent processes configured under $ZZKRN might change from SUPER.SUPER to NULL.NULL. If this occurs on a system where $SYSTEM is using FCDM disk enclosures connected by FCSAs in IOAM enclosures, the system might halt when a system load to the new RVU is attempted.
PAGE 35
New CLuster I/O Module (CLIM) Storage Devices HP introduces (controlled availability) support for next-generation CLIMs and storage devices. The new CLIMs and storage devices require J06.06 and later J-series RVUs. All software required for these components is included with this RVU. See the planning guide for your system for information about the CLIMs and storage devices. The new devices require the J06.06 or later J-series RVU.
PAGE 36
Changes to SSOCLIM Privilege Requirement The privilege for running SSOCLIM, which was SUPER.SUPER for J06.09 and J06.10, has been changed to any SUPER group user. SSOCLIM is run after a fallback. For details, see Complete CLIM Set Up in Chapter 13: “Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations ” (page 117). J06.12 This section provides information only for new features and changes that affect the software installation and upgrade steps for J06.12. See the J06.
PAGE 37
Upgrading a NonStop BladeSystem NB54000c or NB54000c-cg to J06.13 or Later RVUs Before upgrading to the J06.13 RVU or a later RVU, you must obtain the Core License Validation tool (CLICVAL). For more information, refer to the NonStop BladeSystem Planning Guide. Before upgrading to J06.13 or a later J-series RVU, use the CLICVAL tool to verify that the core license file is valid. After upgrading to J06.
PAGE 38
Safeguard Fallback and migration considerations exist for the new Safeguard features. See the J06.14 Release Version Update Compendium for more information. SQL/MX Release 3.2 SQL/MX Release 3.2 replaces SQL/MX Release 2.3.4 as the default SQL/MX version on the SUT starting with J06.14. Users have a choice of staying with the latest SQL/MX Release 2.3.4 SPRs released as Time Critical Fixes (TCFs) or to migrate to SQL/MX Release 3.2.
PAGE 39
4 Upgrade Checklist Use the upgrade checklist in “Upgrade Checklist” (page 40) to track your progress as you perform the tasks required to upgrade to this RVU and the checklists in Table 11 and Table 12 (page 40) to record the information needed when performing these tasks. CAUTION: The upgrade steps must be performed in the order specified in this chapter. NOTE: To perform these upgrade tasks, you need the NonStop System Console (NSC) Installer Guide.
PAGE 40
Table 11 Required Information Checklist, Before You Start (continued) Type of Information Value SWAN2 firmware ServerNet Cluster firmware • Cluster Switch • Cluster Switch (logic board; router-2) SS7 Controller firmware DSM/SCM product version (server and client) Processor type Record the information in Table 12 while you perform the upgrade.
PAGE 41
Table 13 Upgrade Checklist (continued) Task Description Reference 8. If you are migrating from a pre-J06.13 RVU to NB54000c or NB54000c-cg, use the CLICVAL tool to verify your license file. 1. Prior to upgrading to J06.13, use the CLICVAL tool to verify the core license file is valid. For more information on using CLICVAL, refer to the TACL Reference Manual and NonStop BladeSystem Planning Guide.
PAGE 42
Table 13 Upgrade Checklist (continued) Task Description Reference 22. (Optional) Update system • “3. (Conditional): Update the System Firmware” firmware using HP SUM (this applies (page 94) to all NonStop systems running • NonStop Firmware Matrices J-series software except the NS2000 series, but is not always required). 23.
PAGE 43
Table 13 Upgrade Checklist (continued) Task Description Reference Done? 33. For systems with IOAMs, update “Managing ME Firmware and ME FPGA Firmware” IOAM firmware, if necessary. (page 21) and the CSSI web page 34. Update FCSA firmware, if necessary. “Managing ServerNet Adapter Firmware” (page 24) 35. Update G4SA Boot firmware, if necessary. “Managing ServerNet Adapter Firmware” (page 24) 36. Update remaining server blade firmware, if necessary.
PAGE 44
5 Preparing to Upgrade the Server Software (Preinstallation Tasks) Before updating the system console and receiving the SUT, perform these tasks: Back Up Important Files Before you upgrade, create tape backups of critical host applications and files. Back Up NonStop SQL/MP HP recommends that you always have a current backup copy of the $SYSTEM.SYSTEM.ZZSQLCI2 file in case you need to initialize SQL later if you have problems with your new RVU during or after installation. 1.
PAGE 45
NOTE: If you must fall back to this RVU, you need to restore these saved configuration files because the configuration file version must match the NonStop system RVU. If you are upgrading from J06.04 or J06.05, create a subvolume to store the backups, then rename each backup file after you create it. The default file name for the backup is backupgz. Rename these as you create them. For example: 1. CLIMBKUP N1002583 $DATA1.BCKJ0605 2. FUP RENAME $DATA1.BCKJ0605.BACKUPGZ, $DATA1.BCKJ0605.N1002583 3.
PAGE 46
Verify System Processes Check Processor Status 1. Log on to the OSM Low-Level Link. The OSM Low-Level Link appears. 2. Select Processor Status. The Processor Status dialog box appears. The Processor Status for all processors should be Executing NonStop OS. Check System Components 1. Log on to the OSM Service Connection. See the OSM Configuration Guide if you have any problems accessing OSM. After the browser session begins, you can close the original IE window.
PAGE 47
The system name box in the Physical view indicates the overall health of a system by the color of the system icon. Green indicates no problems reported by OSM. Yellow indicates a possible system problem. 2. Double-click to expand the object further to identify components that require attention (yellow or a yellow arrow) or immediate service (red). CAUTION: If a red triangle appears over an object, or if any component is highlighted in red, contact your HP authorized service provider. 3. 4.
PAGE 48
Verify the State of the Internal ServerNet Fabric To verify that the paths and connections within the ServerNet system area network (ServerNet SAN) are properly functional: 1. Log on to the OSM Service Connection. 2. In the tree pane, expand the System object to check for alarms on both Internal ServerNet Fabric objects. 3. Diagnose and resolve any problems that are causing the alarm. If necessary, contact your HP authorized service provider before continuing with the migration.
PAGE 49
127 128 129 130 179 180 181 182 183 184 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 205 206 207 208 209 210 211 231 232 233 234 235 236 237 238 239 240 241 242 243 244 246 247 248 249 250 251 252 253 254 268 293 295 296 299 300 302 331 350 918 2-> $ZM02 $ZM01 $ZM00 $ZLOG $ZCM03 $ZCM02 $ZCM01 $ZCM00 $YOSQA37 $YOSQA3 $SUITES $SUITE2 $SQL11 $SQL10 $SQL09 $SQL08 $SQL07 $SQL06 $SQL05 $SQL04 $SQL03 $SQL02 $SQL01 $SQL00 $SCALE1 $SAS313 $SAS301 $SAS125 $QA2200 $POSQA1 $PITSMP1 $OSS3 $OS
PAGE 50
Verify Disk Drives 1. Enter the SCF STATUS DISK command: > SCF STATUS DISK $* 2. Verify that the STATUS DISK display includes all the disk drives and that the primary, backup, mirror, and mirror-backup paths are all described as STARTED: $SYSTEM TOOLS 48> SCF STATUS DISK $* SCF - T9082H01 - (01MAY08) (15MAR08) - 07/06/2008 10:55:16 System \ATLAS (C) 1986 Tandem (C) 2003 Hewlett Packard Development Company, L.P. STORAGE - Status DISK \ATLAS.
PAGE 51
3. 4. Use the SCF STATUS TAPE, DETAIL command to display the current state of the tape drive. If the status of the tape drive is stopped or not ready, start the tape drive and put the tape drive online. Verify That the CLIMs Are in the Started State 1. Enter the SCF STATUS CLIM command: -> STATUS CLIM $ZZCIP.* 2. Verify that the state of all configured CLIMs is STARTED: CIP Status CLIM \MYSYS.$ZZCIP.
PAGE 52
KMS.SWAPFILE = 1 $SYSTEM.ZSYSSWAP.SWAP01 KMS.SWAPFILE = 2 $SYSTEM.ZSYSSWAP.SWAP02 KMS.SWAPFILE = 3 $SYSTEM.ZSYSSWAP.SWAP03 2. Issue the STATUS SWAPFILE * command to display the peak pages reserved so that you can compare that information to the total amount of swap space available. $SYSTEM TOOLS 50> nskcom STATUS SWAPFILE * NSKCOM - T5838H01 BASE (01OCT07) - Jun 17 2008 Copyright 1995 Compaq Computer Corporation $SYSTEM.SYSTEM.ZSYSCFG KMS.SWAPFILE = 0 $SYSTEM.ZSYSSWAP.SWAP00 KMS.SWAPFILE = 1 $SYSTEM.
PAGE 53
These SPRs must be installed on systems running G-series RVUs if you want the functionality it makes available through Expand-connected H-series or J-series RVU systems. Table 14 Interoperability SPRs for G-Series RVU Systems Connected Through Expand to H-Series or J-Series RVU Systems Minimum SPR Product Name Description Introduced in this RVU T9205D46^ACF TACL Required for remote NEWPROCESS of OCA objects* G06.26 *T9205D46^ACF is required only if you want the functionality it provides.
PAGE 54
These SPRs facilitate software migration and software management operations between nodes running G-series RVUs and nodes running H-series and J-series RVUs: • The T9621D30^ABB, T9674D30^AAM, T9276D30^AAW, and T0448G06^AAA SPRs provide the option of using a G-series RVU system to construct objects that will ultimately run on an H-series or J-series RVU system.
PAGE 55
(running J06.16 or later), you must obtain and use the CLICVAL tool. For more information, see the NonStop BladeSystem Planning Guide. If Necessary, Manually Install the NonStop Software Essentials Server Product HP recommends use of NonStop Software Essentials instead of the Planner Interface for upgrading your RVU. In addition to NonStop Software Essentials being the go-forward strategy, the Planner Interface is not supported on 64-bit NonStop system consoles. Systems running J06.
PAGE 56
6 Installing a SUT for This RVU Using NonStop Software Essentials NOTE: If you do not have NonStop Software Essentials installed, see the NonStop Software Essentials Installation and Quick Start Guide. Alerts for Installing a SUT Do not use this procedure to upgrade more than one system at a time or to install SPRs. For SPRs, see “Using DSM/SCM With NonStop Software Essentials to Install SPRs” (page 131).
PAGE 57
startscm NOTICE: * * * * If the hometerm chosen during INITENV, $zhome, is not currently in a paused state, STARTSCM and DSM/SCM server processes may hang indefinitely.
PAGE 58
11. Click Submit. The request status page appears and is updated automatically. A Status window appears and is updated automatically at regular intervals. 12. While waiting for the request to finish, check: • The status of the request in the Status window. For example: • EMS event messages to see if a cartridge on a non-autoloading drive of the SUT needs to be mounted.
PAGE 59
Create a New Software Revision When you create a new software revision, NonStop Software Essentials selects the products in the SUT that are licensed for your site and replaces any previous versions of the products. The following steps assume that you are creating a new software revision that manages OSS files. If you are not, go to step 5 after you have loaded the Configuration Revisions page in NonStop Software Essentials. These instructions also assume that you have installed OSS.
PAGE 60
b. c. Click the Output tab to view the default output values. Enter the appropriate values in the data fields. NOTE: The alternate name for the $SYSTEM drive defaults to $FC1 for fibre channel drives or $SCSI for SCSI drives. If this default has been changed, then the target volume specified in NonStop Software Essentials for new subvolumes must reflect this change. 4. 5. Click OK to return to the Configuration Revisions page. Click the Create or Edit in the New Revision group box.
PAGE 61
If there are any discrepancies between the set of products included in the previous configuration and the set in your new configuration, the popup shown below is displayed. (These products are removed by default from the system by DSM/SCM during the Build/Apply of the new configuration.) The dialog box lists products installed on the previous revision that are not available on the new SUT.
PAGE 62
7. Keep NonStop Software Essentials open for the next task. Build and Apply the New Software Revision The Build process creates an activation package containing all the products listed in the new software revision. To avoid disrupting other system activities, schedule the Build to run at night and the Apply to run immediately after the build. See the NonStop Software Essentials User’s Guide for information about scheduling the Build/Apply to run at different times.
PAGE 63
3. In the Activation SYSnn: box, enter a unique number to create a new SYSnn subvolume. The value nn must be a two-digit octal number in the range %00...%77. You can issue a FILEINFO command at a TACL prompt to view the SYSnn subvolumes that are currently on your system. > fileinfo $system.*.osimage 4. Make a note of the new SYSnn.
PAGE 64
9. Check EMS messages for more detailed information about your Build/Apply. Click the system name in the System column to view EMS events on that system for this Build/Apply request. When the Build/Apply finishes successfully and a snapshot is received into the host database: • The Request activity summary in the Status window shows that the Build, Apply, Create snapshot, and Receive snapshot activities finished.
PAGE 65
============================================================================== ============================================================================== This software is licensed by Hewlett Packard Development Company L.P. and is subject to restrictions on use, disclosure and copying and is Commercial Software. If a user is an entity of the United States Government, only LIMITED RIGHTS or RESTRICTED RIGHTS are granted. HP and the HP logo are trademarks of Hewlett Packard Development Company L.P.
PAGE 66
===========================More Targets PgDn/PgUp============================= F1-Select F15-Help F16-Return SF16-Exit Ready 4. In the Selection number field, enter the number corresponding to the logical target to which you applied the software (selection 2 in this example), and press F1 to display the Target Menu - Select Action screen.
PAGE 67
Run merge_whatis if zphirnm indicates it is needed. When you finally run ZPHIRNM, the following lines are written to the log: Note: merge_whatis needs to be run to update the man pages. Files in a whatis.frag directory have changed. The merge_whatis is a shell script in /bin. It creates and updates the whatis database used by the OSS shell man, apropos, and whatis commands. You must run the merge_whatis command once against each directory that contains the man page files to be used.
PAGE 68
7 Installing a SUT for This RVU Using the Planner Interface Alerts for Installing a SUT Do not use this procedure to upgrade more than one system at a time or to install SPRs. For SPRs, see “Using DSM/SCM With the Planner Interface to Install SPRs” (page 138). Before you install a SUT or RVU, these requirements must be met: • When managing OSS files with DSM/SCM, check that the OSS Root Name Server $ZPNS is started and running on the DSM/SCM Target. (See “Create a New Software Revision” (page 72).
PAGE 69
PATHWAY CONTROL FILE DATED: 18 APR 2005, 09:56:08 $Z038: WARN - *1079* SERVER CB-001, NO STATIC SERVERS DEFINED $Z038: WARN - *1079* SERVER IS-001, NO STATIC SERVERS DEFINED $Z038: WARN - *1079* SERVER MISERVER, NO STATIC SERVERS DEFINED $Z038: SERVER OM-001, STARTED $Z038: SERVER SM-001, STARTED $Z038: SERVER SM-T-001, STARTED $Z038: SERVER T9154-HELP-SERV, STARTED $Z038: WARN - *1079* SERVER TA-001, NO STATIC SERVERS DEFINED $Z038: WARN - *1079* SERVER TISERVER, NO STATIC SERVERS DEFINED $Z038: WARN - *10
PAGE 70
9. From the list, select the tape drive that contains the SUT, and click OK. The Request Source Options dialog box closes. 10. In the Options group box of the Receive Software Request dialog box, click Scheduling. The Request Scheduling Options dialog box appears. Make the appropriate selections and click OK. The Request Scheduling Options dialog box closes. 11. In the Receive Software Request dialog box, click OK. A Status window appears and is updated automatically at regular intervals. 12.
PAGE 71
• EMS event messages to see if a cartridge on a nonautoloading drive of the SUT needs to be mounted. EMS messages are displayed in these windows: ◦ The EMS Event Stream window ◦ The EMS Events window displayed by DSM/SCM when you click Show EMS events from the Status window ◦ You can also check the Requests window to ensure that the request is finished. (Select Requests>Requests list.
PAGE 72
13. When the request is finished, close the Status and Requests windows. 14. Update the Software in Archive dialog box to show the newly received SUT. Select Window>Refresh. The new SUT appears in the window. 15. Keep the Planner Interface open for the next task. Create a New Software Revision When you create a new software revision, DSM/SCM selects the products in the SUT that are licensed for your site and replaces any previous versions of the products.
PAGE 73
b. c. Click Output to view the default output values. Enter the appropriate values in the data fields. NOTE: The alternate name for the $SYSTEM drive defaults to $FC1 for fibre channel drives or $SCSI for SCSI drives. If this default has been changed, then the target volume specified in the Planner Interface for new subvolumes must reflect this change. d. 3. 4. 5. Click OK. DSM/SCM returns you to the Target Information dialog box. Click OK to return to the Configuration Revisions dialog box.
PAGE 74
6. Click Continue when the Confirmation message appears: If there are any discrepancies between the set of products included in the previous configuration and the set in your new configuration, a warning message appears listing any products missing in the current configuration that were present in the previous configuration. (These products are removed from the system by DSM/SCM during the Build/Apply of the new configuration.) You might receive a warning that certain OSS products are not DSM/SCM enabled.
PAGE 75
7. Keep the Planner Interface open for the next task. Build and Apply the New Software Revision The Build process creates an activation package containing all the products listed in the new software revision. To avoid disrupting other system activity, schedule the Build to run at night and the Apply to run immediately after the build. See the DSM/SCM User’s Guide for information about scheduling the Build/Apply to run at different times. To build and apply the new software revision: 1.
PAGE 76
2. 3. Under Perform steps, select Build, apply & process snapshot. In the Activation SYSnn: box, enter a unique number to create a new SYSnn subvolume. The value nn must be a two-digit octal number in the range %00...%77. You can issue a FILEINFO command at a TACL prompt to view the SYSnn subvolumes that are currently on your system. > fileinfo $system.*.osimage 4. 5. 6. Make a note of the new SYSnn.
PAGE 77
8. (Optional) Confirm that the Spooler is active and not 100 percent full before executing the Build/Apply request. At a TACL prompt, start SPOOLCOM and issue a COLLECT, STATUS command. For example: 12> spoolcom $spls; collect, status COLLECT $S 9. STATE ACTIVE FLAGS 3 , CPU 1 PRI 154 UNIT 4 DATA FILE %FULL $OPS0.SPL.DATA 4 In the Build/Apply Request dialog box, click OK.
PAGE 78
DSM/SCM runs the Build and Apply steps and displays a Status window, which is automatically updated at regular intervals.
PAGE 79
10. Check EMS messages for more detailed information about your Build/Apply: a. In the Events window, click Refresh to see newer messages. b. When finished viewing, click Close. NOTE: If you encounter any problems, see the DSM/SCM User’s Guide or online help. When the Build/Apply finishes successfully and a snapshot is received into the host database: • The Request activity summary in the Status window shows that the Build, Apply, Create snapshot, and Receive snapshot activities finished.
PAGE 80
• The last message in the EMS Events window shows that the input snapshot finished successfully. • The Requests window shows that the request is finished. (Select Requests> Requests list). 11. Close the EMS Events, Status, and Request windows. 12. Exit the DSM/SCM Planner Interface. Print Operator Instructions From the Target Interface (ZPHITI) Print the operator instructions that you edited. 1.
PAGE 81
(c) Hewlett Packard Development Company L.P., 1994-2004 All Rights Reserved ============================================================================== F1-Logon F8-Clear entry F15-Help SF16-Exit Ready 2. Enter your user ID or alias (if necessary) and password and press F1 to log on to the Target Interface.
PAGE 82
DSM Software Configuration Manager Target Menu - Select Action ============================================================================== \WARRIOR Prior snapshot 2007-11-20:12:18:44 DEFAULT Last S/W applied on SYS 00 on 2006-11-22:12:17 Selection number: ============================================================================== Choose an action by entering the selection number of an item from the list below.
PAGE 83
You will run merge_whatis after using ZPHIRNM. If you have OSS configured to run the OSS merge_whatis utility automatically, you can ignore running merge_whatis. Recovery for Problems Installing This RVU SUT or SPRs If you receive an error indication in the Requests, Status, or EMS Events windows, you might have to re-initiate the Build/Apply. See the DSM/SCM Messages Manual to determine the nature and severity of the problem.
PAGE 84
8 Running ZPHIRNM During the Build/Apply phase, DSM/SCM places product files in their subvolumes with temporary (fabricated) file names so that new file names do not conflict with the file names of currently running programs. This chapter describes how to run the ZPHIRNM program on the target system to: • Rename the files that currently have actual file names with fabricated names. These files become obsolete when the new files are renamed.
PAGE 85
• DNSCACHE • DNSHOSTS • DNSLOCAL • DNSREV • DNREVBAK • HOSTS • NETWORKS • PORTCONF • PROTOCOL • RESCONF • SERVICES • SMTPCONF The file names of NonStop TCP/IPv6 that reside on the SUT are: • ztcpip.smplhost • ztcpip.smplprot • ztcpip.smplnetw • ztcpip.smplport • ztcpip.smplresc • ztcpip.smplserv Stop Applications Before running ZPHIRNM: 1. Stop DSM/SCM if it is still running. For example: > VOLUME $dsmscm_vol.
PAGE 86
1. 2. Use the SPOOLCOM;COLLECT $collector-process, LISTOPENS command to identify processes that currently have jobs open. Use the SPOOLCOM;JOB (STATE PRINT) command to determine which jobs are currently printing. Take the appropriate action to ensure that these jobs either terminate when finished or are stopped. After receiving the SPOOLER DRAIN command, the supervisor stops accepting jobs for collection or printing (new opens are rejected with a file-system error 66—device downed).
PAGE 87
Files Processed: Files Files Files Files Files Files Files Files Files Files processed in new configuration ........................... processed in new configuration only ...................... processed in old configuration only ...................... processed that are shared by new and old configuration ... processed & unchanged between new and old configuration .. processed in obsolete TSVs ............................... renamed from real name to fabricated name ................
PAGE 88
Do you want to use a log file with this session? (Y/N): y You may use any file for logging. If you request to use a disk file that doesn't exist, it will be created as an edit file. Please enter a filename: elist00 Log file is open, Zphirnm will now begin processing. ZPHIRNM begins processing and provides status of its progress. 4. If necessary, you can compare the creation dates of the whatis file to the whatis_old file to see if changes occurred: a. Run the more command against the whatis file: more b.
PAGE 89
9 Loading This RVU This chapter describes how to perform a system load on this RVU into the memory of each processor in a NonStop system. NOTE: For additional information about performing a system load of a NonStop system, see the NonStop Operations Guide. By default, one $SYSTEM is already configured. You can select $SYSTEM, FCDM-Load, CLIM-Attached-Load, or an alternate system volume: The $SYSTEM disks must contain the current RVU operating system files for the NonStop system.
PAGE 90
Table 20 System Load Paths in Order of Use for CLIM-Attached-Load (continued) Load Path Description Data Travels From To Processor Over ServerNet Fabric 9 Primary $SYSTEM-P 1 Y 10 Primary $SYSTEM-P 1 X 11 Backup $SYSTEM-B 1 X 12 Backup $SYSTEM-B 1 Y 13 Mirror $SYSTEM-M 1 Y 14 Mirror $SYSTEM-M 1 X 15 Mirror backup $SYSTEM-MB 1 X 16 Mirror backup $SYSTEM-MB 1 Y A CLIM-Attached-Load attempts to load the system from a system disk in the NonStop Storage CLIMs connecte
PAGE 91
You can configure additional alternate system disks. To create an alternate system disk, contact your HP authorized service provider to perform the task. Then use OSM to make the disk available in the Configuration drop-down menu in the System Load dialog box. The alternative system disks are displayed in the Attributes tab under the System object in the OSM Service Connection and are also displayed in the OSM Low-Level Link System Load dialog box in the Configuration shortcut menu.
PAGE 92
Then change SERVER #ZPLS to * SERVER #ZPLS Failure to do this can result in an error during startup of OSS. This error occurs on systems with pre-T0585H01. When Upgrading From J06.05 or an Earlier J-Series RVU: CLIM Software CLIMs configured with the CLIM software released with J06.05 or J06.04 are not compatible with J06.06 and later RVUs. Performing the CLIM upgrade when the processors are halted, as described in “6.
PAGE 93
firmware versions and iLO firmware versions that are currently supported and those that are not. 2. If the blade elements that will be used with the new RVU are already installed, identify the system firmware version currently installed on each of them. The system firmware version, which is stored on the system board of each blade element, is identified as follows: NOTE: If necessary, contact your HP authorized service provider for assistance with these procedures: 3. 4.
PAGE 94
3. 4. If your currently-installed HSS firmware version is no longer supported, perform a system firmware update as described in “4. (Conditional): Update the HSS Firmware” (page 94). If your currently-installed HSS firmware is supported, you do not need to perform an HSS firmware update. 2. Halt the Processors You must halt the processors whenever you migrate your host system from one RVU to another. Perform these steps: 1. Log on to the OSM Low-Level Link. 2.
PAGE 95
NOTE: Prior to NonStop System Console Installer DVD, Update 18, authentication failures could occur when using certain OSM actions, including Update HSS action in OSM Low-Level Link. This problem is automatically fixed when you run the Master Installer on NonStop System Console Installer DVD, Update 18 or later. See Support Note SN 12023 for a workaround option if you do not have the Update 18 or later DVD.
PAGE 96
6. Upgrade the CLIM Software If you have not upgraded the CLIMs online before performing this RVU upgrade, upgrade the CLIM software on each CLIM now. See Upgrading CLIM Software Using OSM Low-Level Link in the Cluster I/O Protocols (CIP) Configuration and Management Manual. 7. (Optional) Update the CLIM Firmware If your system has CLIMs attached, it is important that your CLIM firmware be compatible with your system.
PAGE 97
5. Click Start System. The system load begins. If you want to stop the load process, click Abort in the System Load dialog box. You might wait up to 30 seconds before the abort takes effect. CAUTION: Do not close the System Load dialog box while startup is in progress. If you attempt to close the dialog box, an OSM message box indicates that the system startup process will be stopped if you continue. If you stop a system startup before the operation finishes, the state of your system cannot be predicted.
PAGE 98
Start the MR-Win6530 terminal emulator and open one window each for the CNSL session display and the CLCI session display. If one or more of the startup event stream windows or startup TACL windows does not launch on the system console after a few minutes (5 to 8 minutes), abort system startup, close the OSM Low-Level Link, reboot the system console, and restart the system load using the OSM Low-Level Link again. 6. Monitor the system startup process.
PAGE 99
Completing the System Load (If Necessary) Loading the processors with the CIIN file is usually automatic. However, if the operating system loaded successfully into processor 0 or processor 1, but the commands in the CIIN file do not reload all remaining processors, use the RELOAD TACL commands. You must be super ID (255,nnn) to load the processors. 1. From the system console, log on to the system as a super-group user (255,nnn) and enter: > RELOAD *, PRIME 2.
PAGE 100
3. Verify that the NonStop operating system is working properly: a. Check the startup TACL window to verify that the startup scripts completed successfully. b. Check the startup event stream window and the startup TACL window for error messages. 4. Close the System Startup dialog box. For more information on system loads, see the NonStop Operations Guide.
PAGE 101
10 Resuming Normal Operations Revive the Down Half of the Mirrored Disk If you shut down half of $SYSTEM and other mirrored disks before applying the new RVU, revive the disks now. For instructions on how to bring up the downed half of a mirrored disk, see the Guardian User's Guide. Your Core License For NB54000c and NB5400c-cg systems, use the OSM Read Core License action and verify that the license information is correct for your system. See the NonStop BladeSystem Planning Guide for more information.
PAGE 102
> FUP DUP $SYSTEM.BKUPZSQL.ZZSQLCI2, $SYSTEM.SYSTEM.*, SAVEALL Cold Start the Pathway Configuration 1. 2. Verify your current configuration against the cold start configuration in PATHHOST (or PATHTARG) to check that the current configuration reflects all changes you have made. Run the PATHCOLD macro from the ZDSMSCM subvolume to cold start the Pathway configuration. Start DSM/SCM 1.
PAGE 103
cat1 cat4 cat7 whatis.frag cat2 cat5 cat8 whatis_old cat3 cat6 whatis /usr/share/man: After you run merge_whatis, the directory contains a file named whatis, containing the database. If you have previously installed OSS, a file named whatis_old is present, containing the previous version of the database. Configure Specific Products (Post-System Load) This section contains information about the configuration of various products such as OSS and SMF.
PAGE 104
To copy the sample files: >FUP >FUP >FUP >FUP >FUP >FUP DUP DUP DUP DUP DUP DUP $SYSTEM.ZTCPIP.SMPLHOST, $SYSTEM.ZTCPIP.SMPLPROT, $SYSTEM.ZTCPIP.SMPLNETW, $SYSTEM.ZTCPIP.SMPLPORT, $SYSTEM.ZTCPIP.SMPLRESC, $SYSTEM.ZTCPIP.SMPLSERV, $SYSTEM.ZTCPIP.HOSTS $SYSTEM.ZTCPIP.PROTOCOL $SYSTEM.ZTCPIP.NETWORKS $SYSTEM.ZTCPIP.PORTCONF $SYSTEM.ZTCPIP.RESCONF $SYSTEM.ZTCPIP.
PAGE 105
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: phiwsock 1089/tcp #DSM/SCM Planner Interface For DSM/SCM, the port number is user-definable. The setup default is 1089. In the ZDSMSCM subvolume, check the INITSTAT file for the recently configured TCP/IP port number.
PAGE 106
For those products that are not managed by DSM/SCM, you must install them using COPYOSS or PINSTALL. See the appropriate product’s softdoc and installation instructions. Using OSS Unautomated Configuration and Startup Unautomated configuration and startup is described in Appendix B in the Open System Services Management and Operations Guide. Using OSS EasySetup (T0585) The OSS EasySetup product (T0585) is available for automated setup, as described in the Open System Services Installation Guide.
PAGE 107
1. 2. Configure the WAN manager as described in the WAN Subsystem Configuration and Management Manual. Update the SWAN CLIP firmware. See either the SWAN Concentrator Installation and Support Guide or the SWAN 2 Concentrator Installation and Support Guide. Set Up iTP WebServer If iTP WebServer was installed and was being used with the previous RVU, the same iTP WebServer installation would not work after the RVU upgrade.
PAGE 108
11 Backing Out the DSM/SCM Revision Products That Might Have Fallback Implications Review the J06.nn Release Version Update Compendium for this RVU and product softdocs to make sure that your installed products do not have migration and fallback implications. Open System Services Back up the OSS configuration database files before falling back. For more information, see the Open System Services Management and Operations Guide.
PAGE 109
============================================================================== User ID:______________________ Password:____________ ============================================================================== ============================================================================== This software is licensed by Hewlett Packard Development Company L.P. and is subject to restrictions on use, disclosure and copying and is Commercial Software.
PAGE 110
4 5 6 7 8 9 ===========================More Targets PgDn/PgUp============================= F1-Select F15-Help F16-Return SF16-Exit Ready 2. In the Selection number field, enter the number corresponding to the logical target that you want to back out of (selection 2 in this example), and press F1.
PAGE 111
4. Press F1 to submit the backout request. DSM/SCM automatically reapplies the previous software revision. While the backout request is processing, DSM/SCM displays the Backout - Processing Backout screen, which gives a description of the request, its processing status, and the location of the previous SYSnn software affected by the request.
PAGE 112
1. Stop all applications. Keep OSS running. 2. Update FIRMWARE. Run OSM to check firmware and perform firmware updates. T0287 HALTED STATE SVCS includes firmware changes. T0287 HALTED STATE SVCS includes firmware changes. 3. RUN ZDSMSCM.ZPHIRNM SYS00 4. Check for $0 EMS messages. Correct any errors indicated in the $0 EMS messages. Do not proceed until this step has been successfully completed. 5. Coldload is required. 6. Run merge_whatis if ZPHIRNM indicates it is needed. 7. Restart all applications.
PAGE 113
Monitor the Backout Process Using the Planner Interface 1. 2. Log on to DSM/SCM (Start+Programs+dsm_scm→dsmscm). Select Start+Requests→Requests list. The Requests dialog box appears, showing the type and status of various DSM/SCM requests. 3. From the Request list, double-click your backout request. The Status dialog box displays detailed information about your backout request.
PAGE 114
12 Running ZPHIRNM to Reactivate the Previous Software Revision This step runs the ZPHIRNM program again to change the temporary names of the previous product files back to their actual names. Fallback Considerations for NonStop Software Essentials After ZPHIRNM If after migrating to this RVU, you decide to fall back to an RVU earlier than J06.13, you need to be aware of the fallback considerations for NonStop Software Essentials. NonStop Software Essentials 2.
PAGE 115
• Take the appropriate action to ensure that these jobs either terminate when finished or are stopped. • Drain the Spooler. To drain the Spooler, log on as a super group user (255,n), access SPOOLCOM, and enter the following command: SPOOLCOM> SPOOLER, DRAIN This command causes the Spooler to move from the active to the dormant state. CAUTION: Do not use the TACL STOP command to drain or stop the Spooler. Also, do not issue the TACL STOP command after you have issued the SPOOLCOM DRAIN command.
PAGE 116
6. 7. Review the log file. If ZPHIRNM did not run successfully, correct the problem and rerun. Two types of error and warning messages are issued during the renaming process: • If a fatal error occurs, ZPHIRNM immediately issues an error message and stops. • A nonfatal error is one that affects processing only for a single subvolume. If a nonfatal error occurs, ZPHIRNM issues an error message and attempts to restore the subvolume it is currently processing to its original state.
PAGE 117
13 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations This chapter describes how to perform a system load of the previous RVU and how, as needed, to revert the CLIM software and/or firmware to the previous versions. NOTE: If your NonStop system does not have CLIMs installed, disregard the sections in this chapter that describe CLIM fallback procedures.
PAGE 118
Restoring the CLIMs assumes that you have saved the CLIM configurations by issuing the CLIMBKUP command before upgrading your system, as described in “Back Up CLIM Configuration Files” (page 44) and in the Cluster I/O Protocols (CIP) Configuration and Management Manual. Falling back to previous versions of CLIM software adds approximately one hour for each CLIM to the process of loading the system on the previous RVU.
PAGE 119
5. install it from the CLIM DVD for J-series by following the procedure in the CLuster IO Protocols (CIP) Configuration and Management Manual. Determine if one or more of the CLIMs you are downgrading is being used for DHCP, DNS, and BOOTP services instead of the system consoles on your LAN.
PAGE 120
6. 7. Obtain the system name, netmask, gateway, and IP address for the CLIMs. If this information is unavailable from your environmental documentation, continue with the next step to obtain it directly from your system. Otherwise, skip the next step. Obtain and record the current CLIM configuration information: a. Using the SCF INFO CLIM, DETAIL command, obtain the maintenance interface IP address and NonStop host system name of the CLIM(s) to be downgraded. For example: ->INFO CLIM $ZZCIP.
PAGE 121
6. 7. Click OK when asked “Are you sure you want to do Halts?” When the Action Status box confirms that all processors have halted, close the Processor Status dialog box.
PAGE 122
climconfig ip –add eth0 –ipaddress ip-address -netmask netmask 2. Reboot the CLIMs by entering: reboot 3. Use OSM Low-Level Link to perform the Configure action on each CLIM. In the Configure CLIM dialog box, enter all the information that you gathered before starting this procedure. (In pre-ABK versions of OSM Low-Level Link, the PCI Slot Configuration area shows the possible PCI slot configurations in multiple drop-down menus. (This area is disabled for Storage CLIMs.
PAGE 123
The PCI Slot Configuration area is disabled for Storage CLIMs in pre-ABK, ABK and post ABK versions of OSM Low-Level Link. Sample ABK or Later Versions of OSM Low-Level Link, Storage CLIM Be sure to select the CLIM type for the type of CLIM you are configuring from the Mode of operation pull-down menu. After entering the required information in the dialog box, press Configure.
PAGE 124
Sample ABK or later Version of OSM Low-Level Link Version, IP CLIM 4. 5. Click Yes. The CLIM reboots.
PAGE 125
6. For the two IP CLIMs configured with a Maintenance Provider (usually the first two IP CLIMs, for example, N1002581/N1002582 for NonStop BladeSystems), configure the eth0:0 interface. Using the IP address and netmask of ZTCP0 and ZTCP1 you collected by using the SCF INFO CLIM DETAIL and CLIMCMD interface -info commands prior to starting the downgrade, and using the iLO serial console, enter these commands at the Linux prompt: climconfig interface -add eth0:0 climconfig ip -add eth0:0 -ipaddress 192.168.
PAGE 126
SYSTEM STARTUP COMPLETE, NSK RUNNING ON PROCESSOR n • If the system load fails, check for the appearance of any halt codes or messages. For recovery procedures, see the Processor Halt Codes Manual or Operator Messages Manual. • After the operating system is running on the server, messages are no longer sent to the Details box. See the event messages sent to the startup event stream window. Complete the System Load (If Necessary) Loading the processors with the CIIN file is usually automatic.
PAGE 127
Complete CLIM Setup 1. Establish trust between the CLIM and the NonStop host system. If you are falling back to J06.09 (or to an RVU with T0682H02^ACC) or J06.10 (or to an RVU with T0682H02^ACI), you must run SSOCLIM as SUPER.SUPER. In all cases, you must run SSOCLIM twice, once with the root username and hpnonstop password, and once with the user username and clim password. a. At a TACL prompt, log on as SUPER.SUPER (for a fallback to J06.09 or J06.10) or as any SUPER group user. b. Enter SSOCLIM.
PAGE 128
c. d. Reboot the other set of CLIMs, that is, the other CLIM in each failover pair or the other CLIM in each pair that connects to a particular disk. If the system disk is a SAS disk and you have SAS disk enclosures that contain the system disks (both primary and mirror), check the LUN manager status to be sure they are functional.
PAGE 129
d. e. Select the desired HSS version from the Available HSS versions drop-down menu. Enter the user name and password for every CLIM and the peer NSC to which the selected HSS file needs to be copied and click Copy. 5. If you reimaged a CLIM being used for BOOTP/DHCP/DNS services on your LAN, use the OSM Low-Level Link to copy the HSS file to the CLIM. This action is available before and after system discovery.
PAGE 130
NOTE: See Support Note SN 12023 (OSM application issues with Administrator user on NSC) for instructions on preventing authentication failures from occurring on NonStop System Consoles when using these OSM tools: Down System CLIM Firmware Update, Update HSS and Copy HSS file actions in OSM Low-Level Link, and connecting to a peer NSC from the NonStop Maintenance LAN DHCP DNS Configuration Wizard or the CLIM Boot Service Configuration Wizard.
PAGE 131
A Using DSM/SCM With NonStop Software Essentials to Install SPRs NOTE: Before performing the steps in this appendix install NonStop Software Essentials by using the procedures in the NonStop Software Essentials Installation and Quick Start Guide. SPRs provide new features between RVUs or correct software problems from a previous RVU. This appendix describes tools available for investigating SPRs and instructions on how to install SPRs.
PAGE 132
SPRNOTES You can use SPRNOTES to research an SPR before installing it. Read the installation instructions and considerations documented in the SPRNOTE, which includes: • A summary of SPR contents • Lists of SPRs required for this SPR • Installation considerations, including tasks to perform before and after running DSM/SCM • A summary of problems corrected • A summary of known problems remaining Keep a copy of each SPRNOTE and record the status of the related SPR.
PAGE 133
System number Software release ID 2. 000000 J06.04.00 Issue a TACL FILEINFO command on $system.*.osimage to list the SYSnn subvolumes on your system and determine which one is open. $SYSTEM.SYS00 OSIMAGE CODE 0 EOF LAST MODIFIED OWNER 57354240 15DEC2007 9:57 255,255 CODE 0 EOF LAST MODIFIED 57393152 05APR2008 8:56 RWEP NUNU PExt 200 SExt 200 $SYSTEM.SYS01 OSIMAGE 3.
PAGE 134
1. 2. From the Configuration Revisions page, select the configuration you are updating and click Create in the New Revision group. The new software revision page appears. Select SPRs to be added to the current configuration and click Copy to. Build the New Revision After you have created a new software revision, prepare to install it on your target systems by building it into an executable form: 1. On the New software revision page, click Build/Apply to load the Build/Apply options page. 2.
PAGE 135
> RUN ZPHIRNM $vol.SYSnn where: • $vol specifies the default current system load volume, usually $SYSTEM. • SYSnn specifies the current or new (depending on whether SYSGEN was required) SYSnn subvolume. For example: > RUN ZPHIRNM $system.SYS00 2. 3. When asked if you want to use a log file with the session, enter Y and press Enter. When prompted, enter a file name for the log file. ZPHIRNM issues this message and begins processing: Log file is open, Zphirnm will now begin processing. 4. 5.
PAGE 136
tacl>volume $system.template 4. Rename any existing templates: tacl> rename newres, oldres tacl> rename newnres, oldnres 5. Run INSTALL^TEMPLATES to create updated template files: tacl>install^templates newres newnres $system.ztempl NOTE: Running this macro permanently changes the location of the EMS template files. DSM/SCM creates new EMS templates when it creates a new SYSnn.
PAGE 137
3. 4. 5. 6. 7. 8. Select the processors to be halted. From the Processor Actions list, select Halt. Click Perform action. Click OK when asked if you are sure you want to halt. When the Action Status box confirms that all the processors have been halted, close the Processor Status dialog box. Do not log off the OSM Low-Level Link. Perform a System Load A normal system load consists of loading the operating system from disk into the memory of processor 0 or processor 1.
PAGE 138
B Using DSM/SCM With the Planner Interface to Install SPRs SPRs provide new features between RVUs or correct software problems from a previous RVU. This appendix describes tools available for investigating SPRs and instructions on how to install SPRs. CAUTION: Do not apply any SPR to an RVU without first verifying (by using Scout for NonStop Servers, for example) that the SPR can be installed on that specific J-series RVU. See the J06.
PAGE 139
• A summary of problems corrected • A summary of known problems remaining Keep a copy of each SPRNOTE and record the status of the related SPR. For example, record whether the SPR is not applicable, is already installed, or needs to be installed. Install SPRs Using DSM/SCM With the Planner Interface The steps for using DSM/SCM to install SPRs are the same as those for installing a SUT. Save the Current Configuration First, save the current system configuration database CONFIG file.
PAGE 140
$SYSTEM.SYS01 CODE 0 OSIMAGE 3. EOF LAST MODIFIED 57393152 05APR2008 8:56 OWNER RWEP 255,255 NUNU PExt SExt 200 200 At a TACL prompt, enter a STATUS 0,0 command to see which SYSnn subvolume is currently being used: 3> status 0,0 System \ELI Process Pri PFR %WT Userid Program file 0,0 201 P R 000 255,255 $SYSTEM.SYS01.NMONTOR Swap File Name: $SYSTEM.#0 Hometerm $YMIOP.
PAGE 141
Build the New Revision After you have created a new software revision, prepare to install it on your target systems by building it into an executable form: 1. In the New software revision dialog box, click Build/Apply to list options for your Build/Apply. The Build/Apply Request dialog box appears with all selections dimmed and unavailable. In a few minutes, the dialog box is refreshed with defaults selected. 2. 3. 4.
PAGE 142
Run ZPHIRNM During the Build/Apply phase, DSM/SCM places product files in their subvolumes with temporary (fabricated) file names so that the new files do not conflict with the file names of currently running programs. After the Build/Apply finishes, run the ZPHIRNM program on the target system to: • Rename the files that currently have actual file names with fabricated names. These files become obsolete when the new files are renamed. • 1.
PAGE 143
NOTE: If you run the INSTALL^TEMPLATES macro with no arguments, you are prompted to provide required information. For information on the INSTALL^TEMPLATES arguments, print the usage notes: -> volume $system.zinsaids -> load /keep 1/ TACLMACS -> install^templates /out outdev/ help where outdev is the name of the desired output device. 3. Choose a location on $SYSTEM to keep updated template files: tacl>volume $system.template 4.
PAGE 144
SECURE ($SYSTEM.TEMPLATE.NEWRES,$SYSTEM.TEMPLATE.NEWNRES),"NUNU" *** INSTALL^TEMPLATES: Completed sucessfully *** If a System Load Is Required If OSM is installed and configured, use these instructions to load your RVU. Halt the Processors 1. 2. 3. 4. 5. 6. 7. 8. If necessary, log on to the OSM Low-Level Link. On the toolbar, select Processor Status to open the Processor Status dialog box. Select the processors to be halted. From the Processor Actions list, select Halt. Click Perform action.
PAGE 145
C Copying the DSM/SCM, NonStop Software Essentials, and SWID SPRs from the SUT Using NonStop Software Essentials To better ensure that the SUT installation proceeds smoothly, copy the DSM/SCM, NonStop Software Essentials server, and SWID SPRs located on the SUT to your system and perform the other tasks described in “Copying the DSM/SCM, NonStop Software Essentials, and SWID SPRs from the SUT Using NonStop Software Essentials” (page 145) before you receive and install the RVU SUT.
PAGE 146
Determine the Product Version of NonStop Software Essentials Server on the Host System and the SUT CAUTION: The NonStop Software Essentials server product (T0894H02) has been on the SUT since J06.13. If you are preparing to install a SUT for J06.12 or an earlier J-series RVU, you will not find the NonStop Software Essentials SPR on the SUT. Instead, you must use Scout to install the latest orderable NonStop Software Essentials server SPR on your system when you copy the DSM/SCM and SWID SPRs from the SUT.
PAGE 147
Copy (RESTORE) the DSM/SCM Server, NonStop Software Essentials Server, and SWID Product Versions from the SUT to Disk CAUTION: The NonStop Software Essentials server product SPR (T0894H02) has been on the SUT since J06.13. If you are preparing to install the SUT for J06.
PAGE 148
9. Click Submit to run the request immediately. (The request takes less than 5 minutes to finish.) The Request Status page is loaded into the work panel. Create a New Software Revision for H02 DSM/SCM, NonStop Software Essentials, and SWID SPRs 148 1. From the New Revision page, select the target system being upgraded and the current revision of the system being upgraded. Select Create.
PAGE 149
3. 4. From the New software revision table, verify that the new version of DSM/SCM, NonStop Software Essentials server, and SWID are included in the new software revision. Edit the revision notes for the new revision: a. Click Edit revision notes. The Revision Notes box appears, containing the existing revision notes. b. Enter a description of the changes to the existing text. For example: Added 01/07/14: DSM/SCM, NonStop Essentials server, and SWID c.
PAGE 150
If Migrating to J06.12 or an Earlier RVU, Install the Latest NonStop Software Essentials Server SPR Using Scout The NonStop Software Essentials server SPR is not present on the RVU SUTs J06.12 or earlier. If you are migrating to J06.12 or an earlier J-series RVU, you must install the T0894H02^AAB SPR from Scout to your system disk. Restart Applications You can now start your application software.
PAGE 151
$Z03N: TCP TCP-T, STARTED 2. If necessary, press Enter to have STARTSCM run the IPM6031 TACL macro automatically. This step takes several minutes. STARTSCM: A new version of DSM/SCM has been installed and IPM6031 needs to be run. You can either exit and run IPM6031 manually or continue and IPM6031 will be run for you. Enter to continue or BREAK to exit.
PAGE 152
NOTE: If you cannot cancel the Build request through NonStop Software Essentials, use the DSM/SCM Target Interface (ZPHITI) to cancel the request. See the NonStop Software Essentials User’s Guide and online help for more information. NOTE: If you inadvertently close the Status dialog box, reopen it by selecting Requests> Requests list and then double-clicking the request.
PAGE 153
D Copying the DSM/SCM and SWID SPRs from the SUT Using the Planner Interface NOTE: • You must have installed both the DSM/SCM SPR and the corresponding client version before you receive an RVU SUT. All newly shipped NonStop systems will have the latest DSM/SCM SPR installed. The latest DSM/SCM client version is available only on the SUT unless you have ordered new system consoles.
PAGE 154
You can also bring up the above dialog box with Help/About; this method keeps the window open until you close it. To install the DSM/SCM client, see “Install the DSM/SCM Client Software” (page 162). Copy (RESTORE) the H02 DSM/SCM Product Version to Disk (If Necessary) To copy the H02 product version of DSM/SCM and the SWID product from this RVU to disk, at a TACL prompt, enter the RESTORE command: >RESTORE/OUT $S.#nnn.DSM/$tape, ($*.E6031H02.*, *.E9298H02.
PAGE 155
9. Click OK. You are returned to the Receive Software Request dialog box. 10. Click OK to run the request immediately. (The request takes less than 5 minutes to finish.) The Status dialog box appears. Wait until the display for the Request activity summary appears as Complete, and then close the Status window.
PAGE 156
11. Select Window>Refresh to update the Software in Archive dialog box to include the received software. Create a New Software Revision for H02 DSM/SCM and SWID SPRs 1. In the Configuration Revisions dialog box, select the target system being upgraded and the current revision of the system being upgraded. Select New software revision. DSM/SCM opens the New dialog box listing the products in the last software revision that was built for the target. Allow several minutes for the dialog box to appear. 2.
PAGE 157
and Apply requests are finished and the snapshot is returned. When the Build and Apply requests are finished, the new software is placed in the current SYSnn subvolume. 1. In the New software revision dialog box, click Build/Apply to display the options for your Build/Apply. It might take several minutes for DSM/SCM to assemble the build information. During this time, the Build/Apply Request dialog box appears with all selections dimmed and unavailable.
PAGE 158
Rename the Applied DSM/SCM H02 Files By Running ZPHIRNM 1. Stop DSM/SCM: > VOLUME $dsmscm_vol.ZDSMSCM > RUN STOPSCM where $dsmscm_vol is the DSM/SCM volume. 2. Run ZPHIRNM: > RUN ZPHIRNM $volume.SYSnn where SYSnn is the current SYSnn (because no SYSGEN or system load is required). 3. 4. When asked if you want to use a log file with the session, enter Y. When prompted, enter a file name for the log file. ZPHIRNM displays this message: Log file, filename, was successfully created.
PAGE 159
> RUN STARTSCM These messages appear: 8> startscm DSM/SCM Process Startup Function - STARTSCM - T6031H02 - (31MAR2003) Copyright Hewlett Packard Development Company L.P. 1993-2003 \ NOTICE: * If the hometerm chosen during INITENV, $zhome, * is not currently in a paused state, STARTSCM and DSM/SCM * server processes may hang indefinitely. Be sure this * hometerm has been paused! Because the $ZHOME reliable home-term process is not an interactive process and is always paused, no action is necessary.
PAGE 160
If NonStop Errors Are Displayed See the DSM/SCM EMS Messages manual for information regarding the error message and the DSM/SCM User’s Guide for information on deleting a Build/Apply request. Cancel Pending Build/Apply Requests 1. 2. Select the request to be canceled. Select Requests>Cancel request. The cancel request action takes a few minutes to finish. NOTE: If you cannot cancel the Build request through the DSM/SCM Planner Interface, use the DSM/SCM Target Interface (ZPHITI) to cancel the request.
PAGE 161
6. 7. Make a note of the IP address and port number. Close the dsmscm.ini file. Copy the ZDSMSCM Client File From the Host 1. From the Windows Start menu, select Run and enter the command CMD . An example response is: Microsoft Windows XP [Version 5.1.2600] (C) copyright 1985–2001 Microsoft Corp. C:\Documents and Settings\Administrator > 2. 3. Enter: cd c:\ If a DSMSCM directory does not exist, enter the following at the C:\ prompt to create it: mkdir DSMSCM 4. 5.
PAGE 162
200 PORT command successful. 150 Opening data connection for zdsmexe (192.231.36.1,3212d) (2334 bytes). 226 Binary Transfer complete. ftp: 2334123 bytes received in 0.20 seconds 11441.78Kbytes/sec. ftp> 11. Move zdsm.exe file into the desired folder on the NonStop console, such as c:\DSMSCM or C:\DSMJ06nn. 12. Double click on zdsm.exe to expand the files into the desired folder. Install the DSM/SCM Client Software 1. Using Windows Explorer, double-click Setup.exe.
PAGE 163
You are now prompted to enter an IP port number for the Winsock service that is within a specific range: 8. Enter the IP port number for the Winsock service (see “Determine the Current IP Address and Port Number” (page 160)), and click Next. NOTE: If DSM/SCM is not currently configured to communicate with a host system, accept the default IP port number. You can always change this value later by editing the dsmscm.ini file. You are now prompted to enter the host system name. 9.
PAGE 164
E Updating SWAN Concentrator CLIP Firmware If necessary, you can update the SWAN or SWAN 2 concentrator CLIP firmware after you have completed a system load of the new RVU. See either the SWAN Concentrator Installation and Support Guide or the SWAN 2 Concentrator Installation and Support Guide.
PAGE 165
Acronyms This list provides the full names of acronyms used in this guide. BOOTP Boot protocol. CCSA Common Communications ServerNet adapter. CIIN Command interpreter input. CIP Cluster I/O Protocols. CLCI Cold load command interpreter. CLIM CLuster I/O Module. CLIP Communications line interface processor. CNSL Console. ConMgr Concentrator manager process CRU Customer replaceable unit. DHCP Dynamic Host Configuration Protocol. DLL Dynamic link library.
PAGE 166
PAL Privileged architecture library. PI Planner Interface. PVU Product Version Update. RDF Remote Database Facility. RVU Release version update. RVU Release Version Update. RVUR Release Version Update Revision. SAC ServerNet addressable controller. SAS Serial Attached SCSI. SCSI Small computer system interface. SIM Systems Insight Manager. SIT System image tape. SMF Storage Management Foundation. SMF Storage Management Foundation. SP Service Processor.
PAGE 167
Index Symbols $SYSTEM.ZTCPIP, 103 $SYSTEM.
PAGE 168
configuring SMF, 106 updating TCP/IP configuration files, 103 PREVIEW mode, 87 Processor type in CONFTEXT file, 19 Profiles, target, changing information, 60, 73 PROTOCOL file configuration file location, 104 R RDF, 106 RELOAD command, 99, 126 Remote Database Facility, 106 S SCF testing the tape subsystem, 50 verifying critical processes, 48 verifying disks, 50 Scout for NonStop Servers, 14 ServerNet adapter firmware, 24 SERVICES file, 105 SMF, interoperability and configuration, 106 SOAP 4 see NonStop SO