J06.04 Software Installation and Upgrade Guide HP Part Number: 545780-002 Published: March 2011 Edition: J06.
© Copyright 2008, 2011 Hewlett-Packard Development Company, L.P. 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.
Contents About This Document.....................................................................................8 Supported Release Version Updates (RVUs)..................................................................................8 Intended Audience....................................................................................................................8 New and Changed Information in This Edition..............................................................................
CLuster I/O Module (CLIM).................................................................................................25 4 Upgrade Checklist....................................................................................26 J06.04 Upgrade Checklist.......................................................................................................26 J06.04 Required Information Checklist.......................................................................................
While the Processors are Halted...............................................................................................64 Loading the System.................................................................................................................64 Steps for Loading the System...............................................................................................64 Completing the System Load (If Necessary)...........................................................................
A Using DSM/SCM to Install SPRs.................................................................87 Tools for Managing SPRs.........................................................................................................87 Scout for NonStop Servers..................................................................................................87 DSM/SCM.......................................................................................................................87 SPRNOTES...................
Tables 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Tasks and Tools for Backing Out to the Previous SYSnn .........................................................17 Maintenance Entity (ME) Firmware.....................................................................................19 Maintenance Entity (ME) FPGA..........................................................................................20 Server Blade Firmware Minimum Required Versions..............................................................
About This Document This guide describes: • Upgrading the initial J06.04 RVU through the use of site update tape (SUT) refreshes, if necessary. • Falling back to a previous SYSnn. Supported Release Version Updates (RVUs) This manual supports the J06.04.00 RVU and all subsequent J06.04.nn RVURs unless otherwise noted.
• Installing a J-series RVU from a host system to a remote or separate network-connected target system using an Expand connection or tape. See the DSM/SCM User’s Guide for information on setting up target systems. • Installing and configuring HP NonStop Open System Services (OSS). • Upgrading HP NonStop System Console workstation applications. To install or upgrade HP and third-party system console client software, such as OSM client-based components, see the NonStop System Console Installer Guide.
ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input.
OSM interface, OSM Service Connection, to monitor and perform actions on system and cluster resources. Publishing History Part Number Product Version Publication Date 545780-001 N.A. August 2008 545780-002 N.A. March 2011 HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to docsfeedback@hp.com.
1 Overview of Installing the J06.04 RVU This chapter introduces the basic installation tools and requirements in J-series RVUs, including installing the site update tape (SUT) for a release version update revision (RVUR). For information on installing software product revisions (SPRs), see Appendix A, Using DSM/SCM to Install SPRs. 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.
System Console Requirements A system console is an HP-approved personal computer used to run maintenance and diagnostic software for NonStop S-series and NonStop NS-series servers. New system consoles run one of the following: Windows XP Professional with service pack 2 or Microsoft Windows Server 2003 with service pack 2, and are preconfigured with the required HP and third-party software, including OSM. The DSM/SCM client is also installed and configured.
For more information on configuring and getting started with OSM, see the OSM Migration and Configuration Guide. OSM Client-Based Components Like other system console software, the OSM client-based components are triple-threaded; that is, they support G-Series, H-series, and J-series RVUs. For J06.
• Creating a SIT is not supported in J-series RVUs. • You might need to update both the client and server-side SPRs. For J06.04, the PI screen displays G02/H02 for the client side and H02 for the server side. • As of G06.27, you can manage a J-series target system from a G-series host system. However, you cannot currently manage a G-series target system from a J-series host.
client or Planner Interface installation instructions in the DSM/SCM User’s Guide or Appendix B, Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software. Summary of Software Installation Tasks To install software using DSM/SCM, perform these tasks: 1. Receive new software into the DSM/SCM Archive. When software is received, the files from each product are stored in the DSM/SCM Archive, a holding area for your software. File attributes are stored in the DSM/SCM host database.
SYSTEM_IMPLICIT_CORE_FILES SYSTEM_IMPLICIT_FS_FILES SYSTEM_IMPLICIT_MCP_FILES SYSTEM_IMPLICIT_ETC_FILES TANDEM^IMPLICIT^CORE^FILES; TANDEM^IMPLICIT^FS^FILES; TANDEM^IMPLICIT^MCP^FILES; TANDEM^IMPLICIT^ETC^FILES; This example shows a CONFTEXT file for J06.
2 Managing Microcode and Firmware for NonStop BladeSystems NOTE: Trained HP service providers will update the firmware when they install any field-replaceable units (FRUs). Firmware, unless otherwise noted, is considered customer-updateable. You must manage all microcode and firmware within your system properly, updating it as necessary when new versions become available. Failure to do so can result in a wide range of system problems, from intermittent faults to partial or complete system outages.
If you have legacy NonStop S-series enclosures attached to your BladeSystem (Carrier Grade only), you will also have service processor (SP) firmware to check. For more information on updating SP firmware, see the current G-Series Software Installation and Upgrade Guide.
5. 6. Repeat for the other ServerNet Switch. If the system includes an (optional) enclosure 101, repeat the process for both switches in that enclosure. (The switches in Enclosure 101 are labeled 101.2.5 and 101.3.7.
NOTE: Before connecting a NonStop S-series system to a NonStop BladeSystem (Carrier Grade only) through legacy I/O, you must first update the firmware for both the S-series Gigabit 4-port ServerNet adapter (G4SA) and the Fibre Channel ServerNet adapter (FCSA). Firmware for both the G4SA and FCSA adapters used for S-series systems is not initially compatible with NonStop BladeSystems.
• G4SA. The OSM Service Connection displays G4SA firmware attributes and action under the G4SA SAC object. To check or update G4SA firmware, locate and expand the G4SA, then select its subcomponent G4SA SAC object. In the following example, the firmware attributes show that the current firmware Version is the same as the available Default File Version; no update is necessary.
Table 5 H-Series ServerNet Adapters Product Number Description Host FRU Disk File Name T0630G06^AAN FCSA Flash firmware FCSA I0630 SYSnn subvolume OSM SC or SCF Fibre Channel ServerNet Adapter (FCSA) Installation and Support Guide Default Location Tool Related Information T0612G06 ^AAB FCSA Flash FCSA Boot firmware C0612R00 SYSnn subvolume OSM SC or SCF Fibre Channel ServerNet Adapter (FCSA) Installation and Support Guide T0612G06 ^ AAB G4SA Boot firmware C0612R00 SYSnn subvolume OSM SC
Table 7 Updateable Firmware for S-series interoperability. Product Number Description Host CRU/FRU Disk File Name T1089G06^ABR Service Processor firmware PMF and PMF2; SPCODE9 IOMF and IOMF2 Default Location Tool SYSnn subvolume OSM SC and LLL Additional Firmware for Carrier Grade BladeSystems Table 8 shows additional firmware required for Carrier Grade BladeSystems.
3 J06.04 Installation, Migration, and Fallback Considerations 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.04 and later C++ compilers might require new functions that are in the current C++ Common Runtime Library but not in RVUs earlier than J06.
4 Upgrade Checklist Use the checklist in Table 9 as you perform the tasks required to upgrade to the J06.04 RVU and the checklist in Table 10 (page 27) to record the information needed when performing these tasks. You might have to update the service processor (SP) firmware on NonStop S-series systems for IOMF2 PMF customer-replaceable units (CRUs). J06.04 Upgrade Checklist Table 9 J06.04 Upgrade Checklist 26 Task Description Reference 1. Install the DSM/SCM client and server PVU (if necessary).
Table 9 J06.04 Upgrade Checklist (continued) Task Description Reference Done? 19. Update FCSA firmware. “Managing ServerNet Adapter Firmware” (page 20) 20. Update G4SA Boot firmware. “Managing ServerNet Adapter Firmware” (page 20) 21. Update remaining server blade firmware (if necessary). This upgrade is done via Field Change Order (FCO). 22. Update G4SA Download Code firmware. “Managing ServerNet Adapter Firmware” (page 20) 23. Recover the TCP/IP files (if necessary).
Table 10 J06.
5 Preparing to Upgrade the Server Software (Preinstallation Tasks) This chapter describes tasks that are needed before updating the system console and receiving the SUT.
Back Up TMF Files Use the OBEYFORM option available in TMFCOM INFO commands to save current configuration information in command files. Record the Current SYSnn Identify and record the current SYSnn subvolume on your system. You will have to specify this SYSnn subvolume if you need to fall back from the J06.04 RVU. At a TACL prompt, issue the status command to determine the current SYSnn subvolume.
• “Verify Tape Drives (If Necessary)” (page 35) • “Check the Status of the Spooler Collector” (page 35) • “Check for Sufficient Swap File Space” (page 35) Check Processor Status 1. Log on to the OSM Low-Level Link. The OSM Low-Level Link Application 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.
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 service provider. 3. 4.
NOTE: If the Halt Code or Halt Flag attributes do not match these values, see the Processor Halt Codes Manual. 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. 2. 3. Log on to the OSM Service Connection. In the tree pane, expand the System object to check for alarms on both Internal ServerNet Fabric objects. Diagnose and resolve any problems that are causing the alarm.
Verify Critical System Processes 1. From a TACL prompt, log on to the system using the super ID (255,255). Enter the LISTDEV command: > SCF LISTDEV $ADBIT RESULTS 18> scf SCF - T9082H01 - (01MAY08) (15MAR08) - 05/09/2008 16:13:56 System \ATLAS (C) 1986 Tandem (C) 2003 Hewlett Packard Development Company, L.P. (Invoking \ATLAS.$SYSTEM.STARTUP.
STORAGE - Status DISK \ATLAS.$ADAUD LDev Primary Backup Mirror 151 *STARTED STARTED MirrorBackup *STARTED STORAGE - Status DISK \ATLAS.$ADBIT LDev Primary Backup Mirror 150 *STARTED STARTED MirrorBackup *STARTED STORAGE - Status DISK \ATLAS.
KMSF swap files need to be larger than in G-series RVUs. The best practice is to monitor swap file usage. See the Kernel-Managed Swap Facility (KMSF) Manual for information on configuring swap file space. To check the size of the configured swap files for each processor: 1. At a TACL prompt, start NSKCOM: $SYSTEM STARTUP 5> nskcom NSKCOM - T5838H01 BASE (01OCT07) - Apr 15 2008 Copyright 1995 Compaq Computer Corporation $SYSTEM.SYSTEM.ZSYSCFG KMS.SWAPFILE = 0 $SYSTEM.ZSYSSWAP.SWAP00 KMS.
Install Node Interoperability SPRs Node interoperability is the ability of the nodes (systems) in a network of NonStop operating system nodes to communicate and interact with each other. Table 11lists the specific SPRs that must be installed on NonStop S-series systems for compatibility and interoperability with NonStop Bladesystems. Table 12 lists the specific SPRs that must be installed on NonStop NS-series systems for compatibility and interoperability with NonStop BladeSystems.
6 Installing a SUT for the J06.04 RVU Installing a new RVU or a SUT involves these DSM/SCM tasks: 1. 2. 3. “Receive New Software Into the Archive” (page 38) “Create a New Software Revision” (page 43) “Build and Apply the New Software Revision” (page 47) Alerts for Installing a SUT Do not use this procedure to upgrade more than one NonStop BladeSystem at a time or to install SPRs. For SPRs, see Appendix A, Using DSM/SCM to Install SPRs.
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.
5. 6. 7. In the Receive Options group box, do one of the following, depending on your system environment: • Select Receive only changed files (default) • Select Receive all files (recommended for the new RVU) Under Software name, select Provided by planner and enter a name for the revision. In the Options group box, click Input source. The Request Source Options dialog box appears. 8. 9. Select Tape drive. From the list, select the tape drive that contains the SUT, 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. While waiting for the request to finish, check: • The status of the request in the Status window.
• 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.) For example: 42 Installing a SUT for the J06.
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.
#ZTA07 #ZTA08 #ZTA09 #ZTA10 #ZTA11 #ZTA12 #ZTA13 #ZTA14 #ZTA15 STOPPED STOPPED STOPPED STOPPED STOPPED STOPPED STOPPED STOPPED STOPPED Total Errors = 0 $ADBIT TESTBIT 12> 1. 2. 0 0 0 0 0 0 0 0 0 Total Warnings = 0 In the DSM/SCM Planner Interface, in the Configuration Revisions dialog box, select the target configuration. Select Maintain>Target Maintenance>Modify. a. Check that the Manage OSS Files option is selected. b. c. 44 0 0 0 0 0 0 0 0 0 Click Output to view the default output values.
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. Click OK to return to the Planner Interface. Select New software revision.
The Non SUT Products screen might appear: The dialog box lists non-SUT products installed on the previous SYSnn that are not available on the new configuration. You can retain non-SUT or third-party products from your current configuration into the new revision: • To include one or more products in the configuration to be built, select the products and click Continue. • To include all products, click Select All and click Continue. The New software revision list now displays the new revision level (J06.
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.
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.
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.
DSM/SCM runs the Build and Apply steps and displays a Status window, which is automatically updated at regular intervals. For example: 50 Installing a SUT for the J06.
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.
• 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.
T6031H01 11NOV2007 (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.
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.
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. 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 an J06.
7 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.
Back Up (Copy) Files in the $SYSTEM.ZTCPIP Subvolume (Best Practice) Make backup copies of these files in the $SYSTEM.ZTCPIP subvolume before running ZPHIRNM, which overwrites them with sample versions. You might need previous versions for reference or fallback: • DNSBAK • DNSBOOT • 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.
NOTE: Your site might have macros or OSS shell scripts set up to start and stop applications, devices, and processes. Drain the Spooler (Optional) Use the SPOOLCOM;SPOOLER,DRAIN command to perform an orderly shutdown of the spooler. Failure to do so can cause problems during a warm start of the spooler. Before executing the SPOOLCOM;SPOOLER,DRAIN command: 1. 2. Use the SPOOLCOM;COLLECT $collector-process, LISTOPENS command to identify processes that currently have jobs open.
Statistics: TSVs: TSVs TSVs TSVs TSVs TSVs in new in old in new in old shared configuration .................. configuration .................. configuration only ............. configuration only ............. by new and old configurations .. 129 130 0 1 129 TSVs processed in new config ............... TSVs processed in old config (obsolete) .... 129 1 Files Processed: Files Files Files Files Files Files Files Files Files Files processed in new configuration ...........................
where: 2. 3. • $vol specifies the default current system load volume, usually $SYSTEM. • SYSnn specifies the subvolume to which you just applied software. The SYSnn subvolume must match the activation SYSnn that you specified earlier during the Build/Apply phase. 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: 6> run zphirnm $system.
8 Loading the J06.04 RVU This chapter describes how to perform a system load of the J06.04 RVU into the memory of each processor in a NonStop BladeSystem. NOTE: For detailed information on performing a system load of a NonStop BladeSystem, see Chapter 15 in 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: • A load from $SYSTEM attempts to load the system from a disk in group, module, slot 11.1.
Table 14 System Load Paths in Order of Use for CLIM Attached-Load Load Path Description Data Travels From To Processor Over ServerNet Fabric 1 Primary $SYSTEM-P 0 X 2 Primary $SYSTEM-P 0 Y 3 Backup $SYSTEM-B 0 Y 4 Backup $SYSTEM-B 0 X 5 Mirror $SYSTEM-M 0 X 6 Mirror $SYSTEM-M 0 Y 7 Mirror backup $SYSTEM-MB 0 Y 8 Mirror backup $SYSTEM-MB 0 X 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 Mir
• You can configure additional alternate system disks. To create an alternate system disk, see the NonStop BladeSystem Hardware Installation Manual. 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.
See the applicable softdocs for details. See Section : “Managing Microcode and Firmware” for a description of the firmware installation procedure. Halt the Processors 1. 2. 3. 4. 5. 6. 7. Log on to the OSM Low-Level Link. On the toolbar, click Processor Status to display the Processor Status dialog box. Under Processor Status, select all processors. From the Processor Actions list, select Halt. Click Perform action.
3. In the SYSnn box, enter nn, which is the number of the system subvolume that contains the version of the operating system you will load, the version created by DSM/SCM. a. Under Configuration File, select Current (CONFIG), the default configuration file that represents the configuration currently running. b. Under SYSnn and CIIN Option, verify that the CIIN Disabled option is not selected. The CIIN file must be enabled because it contains commands needed to start the server.
Two windows for startup event stream windows (CNSLS) and two startup TACL windows (CLCIs) are automatically launched. It might take a few seconds before the windows appear. 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.
2. 3. Close the Processor Status dialog box. 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, the NonStop Operations Guide.
9 Resuming Normal Operations This chapter describes tasks that might need to be performed after a system load. Start User and System Applications You can now start your application software. Follow your site’s procedures for executing the system configuration and startup (command) files to accomplish this. DSM/SCM is often started automatically by a system command file. If not, you must start it manually as described next. Before Starting DSM/SCM Initialize SQL for NonStop SQL/MP 1.
Start DSM/SCM 1. From the ZDSM/SCM subvolume, start DSM/SCM: > RUN STARTSCM Because the $ZHOME reliable home-term process is not an interactive process and is always paused, no action is necessary. 2. Press Enter. STARTSCM automatically runs the IP6031 TACL macro. This step can take several minutes. Run merge_whatis After coldloading the system, run the OSS merge_whatis command. (ZPHIRNM notifies you if you need to run it.
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. See product-specific documentation for more information on installation and configuration.
>FUP >FUP >FUP >FUP >FUP DUP DUP DUP DUP DUP $SYSTEM.ZTCPIP.SMPLPROT, $SYSTEM.ZTCPIP.SMPLNETW, $SYSTEM.ZTCPIP.SMPLPORT, $SYSTEM.ZTCPIP.SMPLRESC, $SYSTEM.ZTCPIP.SMPLSERV, $SYSTEM.ZTCPIP.PROTOCOL $SYSTEM.ZTCPIP.NETWORKS $SYSTEM.ZTCPIP.PORTCONF $SYSTEM.ZTCPIP.RESCONF $SYSTEM.ZTCPIP.SERVICES Step 2: Check the PROTOCOL File (Optional) CAUTION: Even if you are running TCP/IPv6 in IPv4 or conventional TCP/IP mode, you must make sure that the PROTOCOL file contains ipv6 and icmpv6 entries.
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. INITSTAT is created by DSM/SCM when INITENV is run.
NOTE: To preserve the original inetd.conf file—before using COPYOSS or PINSTALL—the following steps must be done to prevent COPYOSS or PINSTALL from overwriting the original inetd.conf file: • Save the original inetd.conf file by using the command: > mv inetd.conf smplinetd.conf • After running COPYOSS or PINSTALL, if the original inetd.conf file needs to be restored, use the command: > mv smplinetd.conf inetd.
1. 2. 74 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.
10 Backing Out the DSM/SCM Revision This chapter describes: • Products that might have fallback implications. Before falling back or backing out the revision, review the appropriate product softdocs. • Using DSM/SCM to back out the revision. Products That Might Have Fallback Implications Review the J06.04 Release Version Update Compendium and product softdocs to make sure that your installed products do not have migration implications.
Start the Target Interface (ZPHITI) 1.
\ELI Prior snapshot 2007-04-14:18:03:03 Selection number: ============================================================================== Choose a target selection number from the list below. Status information is shown for requests still in progress. ============================================================================== 1 NEW CONFIG 2 DEFAULT 3 4 5 6 7 8 9 ===========================More Targets PgDn/PgUp============================= F1-Select F15-Help F16-Return SF16-Exit Ready 2.
Backout target revision will be performed: From: SYS 02 applied on 2007-04-14:18:01 To: SYS 01 applied on 2007-04-17:15:41 ============================================================================== F1-Submit request F15-Help F16-Return SF16-Exit Ready 4. Press F1 to submit the backout request. DSM/SCM automatically reapplies the previous software revision.
============================================================================== Placement of files for this Backout is complete. To activate the software that has been placed follow the operator instructions displayed below. =============================================================================== Activation Instructions for \BITDRP BITDRP These are general instructions that were determined from configuration attributes.
Backing Out the DSM/SCM Revision
11 Running ZPHIRNM to Reactivate the Previous Software Revision This chapter describes how to run the ZPHIRNM program again to change the temporary names of the previous product files back to their actual names. Alerts Before running ZPHIRNM: • Applications that use files that are being replaced should not be running. To avoid any possibility of conflict, stop all applications, except for the TMF subsystem, before running ZPHIRNM. • You must have rename (purge) access to all files being renamed.
without actually updating files or activating the configuration. In PREVIEW mode, ZPHIRNM indicates whether or not TMF needs to be up when running ZPHIRNM. Run ZPHIRNM 1. At a TACL prompt, enter from the DSM/SCM subvolume: > RUN ZPHIRNM $vol.SYSnn where: • $vol specifies the default current system load volume, usually $SYSTEM. • SYSnn specifies the SYSnn subvolume named previously in the backout request. For example: > RUN ZPHIRNM $system.SYS00 2. 3. 4.
12 Loading the Previous RVU and Resuming Normal Operations This chapter describes how to perform a system load of the previous RVU of the NonStop operating system into the memory of each processor in a NonStop BladeSystem. Alerts Before performing a system load: • Before halting the processors, stop running applications, including TMF. NOTE: To stop TMF, at a TACL prompt, enter: • Do not close the System Startup dialog box while startup is in progress.
See the applicable softdocs for details. Halt the Processors 1. 2. 3. 4. 5. 6. 7. Log on to the OSM Low-Level Link. On the toolbar, click Processor Status to display the Processor Status dialog box. In the Processor Status box, select all processors. From the Processor Actions list, select Halt. Click Perform action. 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.
5. In the System Load dialog box, 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.
Verifying That the System Is Started Verify that each processor is running the operating system: 1. 2. 86 From the Summary menu in the OSM Low-Level Link, select Processor Status. The Processor Status dialog box should show each processor to be Executing NonStop OS.
A Using DSM/SCM 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.
• 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 With DSM/SCM The steps for using DSM/SCM to install SPRs are basically the same as those for installing a SUT. Save the Current Configuration First, save the current system configuration database CONFIG file. Use the SCF SAVE command: 1.
OSIMAGE 0 57354240 15DEC2007 9:57 255,255 NUNU 200 200 $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.
1. In the Configuration Revisions dialog box, select the configuration you are updating, and click New Software Revision. The New software revision dialog box appears. 2. In the Software in Archive dialog box, 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.
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.
-> load /keep 1/ TACLMACS 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.
>$SYSTEM.SYS00.FUP /NAME $Z03M,INV :INBUF.1,OUTV :OUTBUF.1/ File Utility Program - T6553D45 - (14APR2000) System \TINY Copyright Tandem Computers Incorporated 1981, 1983, 1985-2000 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 application.
B Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software NOTE: • For NonStop BladeSystems, you must have installed both the DSM/SCM SPR and the corresponding client version before you receive an RVU SUT. For J06.04, all newly shipped NonStop BladeSystems 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.
VPROC - T9617H01 - (01 OCT 2004) SYSTEM \DRP08 Date 12 MAY 2006, 18:20:13 Copyright 2004 Hewlett-Packard Development Company, L.P. $DSMSCM.ZDSMSCM.TAEXE Binder timestamp: Version procedure: Version procedure: Target CPU: OCA timestamp: Privileged code: \DRP08.$DSMSCM.ZDSMSCM 4> 1DEC2005 16:31:25 S7032H06^01OCT2004^SWARCCP^H01 T6031H02_01NOV2007_16DECACH UNSPECIFIED 16DEC2007 16:36:28 YES Determine the Latest SWID Product Using the VPROC command, determine the SWID PVU: \DRP08.$SYSTEM.
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 the J06.04 RVU to disk, at a TACL prompt, enter the RESTORE command: >RESTORE/OUT $S.#nnn.DSM/$tape, ($*.E6031H02.*, *.E9298H02.*), VOL $DSMSCM, LISTALL where nnn is the RVU number (J06) and where $tape is the name of the tape drive containing the J06.04 RVU. Receive the H02 SWID and DSM/SCM SPRs 1. 2. 3. 4.
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. For example: 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.
Build and Apply the DSM/SCM H02 Software Product Revision The Build process creates an activation package of products contained in the new software revision. During the Apply process, the activation package is transferred to the target system. When the Apply request is finished, a snapshot is automatically created and returned to the host. Because you are building and applying only a few files, it should take less than an hour before the Build and Apply requests are finished and the snapshot is returned.
5. 6. 7. Check EMS messages for more detailed information about your Build/Apply: • From the Status window, click Show EMS events. • In the EMS Events window, click Refresh to see newer messages. • When finished viewing, click Close. To confirm that the Build and Apply tasks finish successfully and that a snapshot has been received into the host database, wait until the status shows that all requests are complete. Select Window>Refresh.
Before Starting DSM/SCM 1. Check that TMF is started: > TMFCOM STATUS TMF 2. 3. 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. If necessary, run the PATHCOLD macro from the ZDSMSCM subvolume to cold start the Pathway configuration. Start DSM/SCM 1.
> volume $dsmscm_vol.ZDSMSCM > vproc taexe > vproc cbexe This example shows the H02 product version of DSM/SCM after DSM/SCM has been activated. (Bold lettering is used to show the VPROC command and the latest version): \DRP08.$DSMSCM.ZDSMSCM 2> vproc cbexe VPROC - T9617H01 - (01 OCT 2004) SYSTEM \DRP08 Date 16 Jan 2007, 18:20:02 Copyright 2004 Hewlett-Packard Development Company, L.P. $DSMSCM.ZDSMSCM.
Cancel Pending Build/Apply Requests NOTE: If you inadvertently close the Status dialog box, reopen it by selecting Requests> Requests list and then double-clicking the request. 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.
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.
250 CWD command successful 10. Enter: get zdsmexe zdsm.exe. An example response is: 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> Install the DSM/SCM Client Software 1. Using Windows Explorer, double-click Setup.exe. A DSM/SCM Setup screen appears, and an Enter Object Manager Server Class dialog box appears with the default OM-001. 2.
NOTE: Private software product groups can be used only by the planner who creates the grouping. Shared software product groups can be used by other planners. For more information on these options, see the DSM/SCM User’s Guide. The Enter CNFGINFO Process Name dialog box appears with the default name $ZPHC. 4. Click Next to accept the default. The Setup Type dialog box appears: 5. Check that WINSOCK is selected. Click Next.
6. Click Next to accept the default. You are now prompted to enter an IP address: 7. Enter the IP address for the host system with which DSM/SCM communicates (see “Determine the Current IP Address and Port Number” (page 102)), and click Next. NOTE: If DSM/SCM is not currently configured to communicate with a host system, accept the default IP address. You can always change this value later by editing the dsmscm.ini file.
8. Enter the IP port number for the Winsock service (see “Determine the Current IP Address and Port Number” (page 102)), 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.
10. Click No. The setup program adds the DSM/SCM client software to the Windows Start>Programs menu. You can start the DSM/SCM Planner Interface or CNFGINFO tool from the Start>Programs>DSM_SCM submenu.
C 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.
Glossary A7CINFO file. A configuration file distributed with OSS products that contains information on the contents of all pax (archive) files of an OSS DSV. ALLPROCESSORS paragraph A required paragraph in the CONFTEXT configuration file that contains attributes defining the HP NonStop™ operating system image for all system processors. The ALLPROCESSORS paragraph follows the optional DEFINES paragraph.
Distributed Systems Management/Software Configuration Manager (DSM/SCM) A graphical user interface (GUI)-based program that installs new software and creates a new HP NonStop™ operating system. DSM/SCM creates a new software revision and activates the new software on the target system. distribution subvolume (DSV) A subvolume containing program files for a particular software product along with the release version update (RVU) document (softdoc) file for that product.
primitives, routines implicitly called from native-compiled code, emulators for TNS floating-point arithmetic, and emulators for privileged-only or long-running TNS machine operations. Open System Services (OSS) An open system environment available for interactive or programmatic use with the HP NonStop operating system. Processes that run in the OSS environment usually use the OSS application program interface.
Index Symbols $SYSTEM.ZTCPIP, 70 $SYSTEM.
SCF testing the tape subsystem, 35 verifying critical processes, 34 verifying disks, 34 ServerNet adapter firmware, 20 SERVICES file, 72 SMF, interoperability and configuration, 73 Software revision, 16 Spooler backing up, command for, 58 checking status of collector, 35 COLLECT, STATUS command, 49, 75, 90 DRAIN command, 58 draining, 29 SPRNOTES, 87 SPRs interoperability, 37 Status dialog box, reopening, 55, 102 SUT, maximum size of, 12 SWAN and SWAN 2 concentrator firmware, 23 Swap file space, checking , 3
