J06.
© Copyright 2010, 2011, 2012 Hewlett-Packard Development Company, L.P. © Copyright 2009, 2010, 2011, 2012 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.
Contents About This Document...................................................................................10 Supported RVUs.....................................................................................................................10 Intended Audience..................................................................................................................10 New and Changed Information in This Edition............................................................................
Compiling C++ Programs to Run on RVUs Earlier Than J06.04.................................................30 SQL/MX Versioning Feature Removed..................................................................................30 CLIM................................................................................................................................30 J06.05..................................................................................................................................
Recovery for Problems Installing This RVU SUT or SPRs.................................................................61 Cancel Pending Build/Apply Requests..................................................................................61 7 Installing a SUT for This RVU Using the Planner Interface................................62 Alerts for Installing a SUT.........................................................................................................62 Back Up Important Files..................
Run the inetd Process.....................................................................................................96 Using OSS Unautomated Configuration and Startup..........................................................96 Using OSS EasySetup (T0585)........................................................................................97 Configure SMF (Optional)...................................................................................................
Receive the SPR Into the DSM/SCM Archive........................................................................134 Before Starting DSM/SCM...........................................................................................134 Bring the SPR Into the DSM/SCM Archive.......................................................................134 Create a New Software Configuration That Includes the SPR..................................................134 Build the New Revision................................
D Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software ..153 Alerts..................................................................................................................................153 Determine the Product Version of DSM/SCM on the Host System............................................153 Determine the Latest SWID Product.....................................................................................153 Determine the Product Version of DSM/SCM on the Client........
Tables 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Tasks and Tools for Backing Out to the Previous SYSnn .........................................................21 Maintenance Entity (ME) Firmware File Names and Locations................................................23 Maintenance Entity (ME) FPGA File Names and Locations.....................................................24 Server Blade Firmware for NonStop BladeSystems Systems....................................................
About This Document This guide describes: • Upgrading the initial J06.09 RVU through the use of SUT refreshes, if necessary. • Falling back to a previous SYSnn. Supported RVUs This manual supports the J06.09.00 RVU and all subsequent J06.09.nn RVUs unless otherwise noted.
The 608001-008 edition contained a change to step 3 in “Complete CLIM Setup” (page 128) for the need to reboot Storage CLIMs after executing the clearlog command. The 608001-007 edition had the requirements for interoperability SPRs for NonStop SQL/MX 2.3.4 removed as this issue has been fixed in the product. The 608001-006 edition contained a change to the privileges required for running SSOCLIM. See “Complete CLIM Setup” (page 128).
• Installing and configuring OSM server components. To install and configure OSM server components, and start using client-based components, see the OSM Migration and Configuration Guide. • Installing, configuring, and migrating to HP NonStop SQL/MX. The SQL/MX Installation and Management Guide provides step-by-step instructions for installing and configuring NonStop SQL/MX.
Related Information NOTE: Many of the documents referenced in this guide are located in the NTL, which has moved to the HP Business Support Center (BSC) at http://www.hp.com/go/nonstop-docs. See Tips for Locating NonStop Documents in the BSC for information about locating NonStop documents. • The CLuster I/O Module (CLIM) Software Compatibility Reference provides the compatibility information of CLIM DVD SPRs and host RVUs.
1 Overview of Installing This RVU For information on installing SPRs, see “Using DSM/SCM and NonStop Software Essentials to Install SPRs” (page 132) or “Using DSM/SCM and Planner Interface to Install SPRs” (page 139). 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.
Online help for using Scout is available on the Scout Web site. • The DSM/SCM Planner Interface or Scout provides a facility for viewing and printing 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 system console is an HP-approved personal computer used to run maintenance and diagnostic software for NonStop servers.
• • ◦ FCSA ◦ G4SA, located under the G4SA SAC object ◦ Fibre Channel disk drives and EMUs, located within FCDMs ◦ SWAN CLIPs ◦ Legacy S-series components supported in J-series RVUs Recent enhancements include system-level actions to: ◦ Perform data sanitization. ◦ Configure system as a member of a BladeCluster.
NOTE: The OSM Notification Director has been removed from the NSC DVD; it will not function on consoles running Windows 2008 Server. Its functionality has been replaced by HP Insight Remote Support Advanced. For more information, see "Insight Remote Support Advanced for NonStop," in the NonStop Technical Library. For more information on OSM client applications, see the OSM Migration and Configuration Guide or the online help available from within each application.
• 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 system. • When you upgrade the client and server SPRs for DSM/SCM, you must also upgrade the SWID product (T9298H02) at the same time to avoid a fingerprint or mismatched file problem. For this RVU, SWID is already installed. OSBUILD SPR WARNING! If a J06.
and Quick Start Guide for how to install it.) If you did not order new system consoles, download HP SIM and NonStop Software Essentials from Scout: • T0895 V02 AAA (Windows) • T0996 V02 AAA (Linux) • T0894 H02 AAA (NonStop Software Essentials server) Downloads for HP SIM are here: www.hp.com/go/hpsim. For instructions on installing NonStop Software Essentials, see the NonStop Software Essentials Installation and Quick Start Guide.
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.
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.
2 Managing Microcode and Firmware NOTE: Trained HP 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.
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 ME firmware for IME in VIO enclosures (see Caution below) VIO enclosure logic board M1805 SYSnn subvolume For more information on managing ME firmware, see: • The planning guide or hardware insta
To use the OSM Service Connection to update the ME firmware for VIO 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. System > Group nnn > VIO Module > VIO Logic Board Right-click the VIO Logic Board object and select Actions. In the Actions dialog box, select ME Firmware Update and click Perform Action. Monitor the update.
Table 5 Blade Element Firmware for NonStop NS2000 Series Systems Firmware Name Product Description Halted State Services and HPI Loader T8004 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. This firmware is packaged as part of the DVD containing T8004 and cannot be updated independently. DISKBOOT Firmware Used during a system load.
• 26 FCSA. The FCSA has two ports that allow connection to external fibre-channel-enabled devices. You might need to update these firmware files using either SCF or OSM. ◦ The flash boot firmware (T0630G06) contains version information about the boot firmware located in the FCSA FLASH memory. The boot firmware runs on every FCSA after power on and after hardware or firmware errors, and is re-downloaded to initialize the adapter and to accept downloaded firmware from the processor.
• 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.
Managing SWAN and SWAN 2 Concentrator Firmware Both SWAN and SWAN2 are supported in J-series RVUs, and OSM is used to update the firmware. SCF can also be used. For procedures to update the firmware, see either the SWAN Concentrator Installation and Support Guide or the SWAN 2 Concentrator Installation and Support Guide. NOTE: Firmware levels for each component are located in the NonStop Firmware Matrices document.
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 applications, and connecting to a peer NSC from the NonStop Maintenance LAN DHCP DNS Configuration Wizard or the CLIM Boot Service Configuration Wizard.
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.
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.
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.
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.
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.
4 Upgrade Checklist Use the upgrade checklist in “Upgrade Checklist” (page 36) to track your progress as you perform the tasks required to upgrade to this RVU and the checklists in Table 10 and Table 11 (page 36) 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.
Table 10 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 11 while you perform the upgrade.
Table 12 Upgrade Checklist (continued) Task Description Reference 8. Install and configure the latest Halted State Services firmware, if necessary (includes DISKBOOT and ISP1040 firmware). Note: This step is not applicable to NonStop NS2000 series systems. • NonStop System Console (NSC) Installer Guide (procedures) 9. Verify system operations. “Verify System Processes” (page 41) Done? • NonStop Firmware Matrices (firmware levels reference) 10.
Table 12 Upgrade Checklist (continued) Task Description Reference 23. Load the system with new this RVU. Loading the system, chapter 6. 24. Update S-series interoperability firmware, if necessary. “Managing S-Series Interoperability Firmware” (page 29) 25. Update ME and ME FPGA firmware, if necessary. “Updating ME Firmware” (page 22) 26. For systems with IOAMs, update “Managing ME Firmware and ME FPGA Firmware” IOAM firmware, if necessary. (page 22) and the CSSI web page 27.
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.
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.
Verify System Processes 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. See the OSM Migration and Configuration Guide if you have any problems accessing OSM. After the browser session begins, you can close the original IE window.
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 Service Provider. 3. 4.
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 Service Provider before continuing with the migration.
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.
151 *STARTED STARTED *STARTED STORAGE - Status DISK \ATLAS.$ADBIT LDev Primary Backup Mirror 150 *STARTED STARTED *STARTED STORAGE - Status DISK \ATLAS.
ZCSAM PROV1 STARTED STARTED Started Invalid OFF (0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15) Check the Status of the Spooler Collector Check that the spooler collector is active and not 100 percent full. At a TACL prompt, start SPOOLCOM and issue a COLLECT, STATUS command. For example: 1> spoolcom $spls; collect, status COLLECT $S STATE ACTIVE FLAGS 3 , CPU 1 PRI 154 UNIT 4 DATA FILE $OPS0.SPL.
Threshold 86959 CPU pages * Default swapfile extents may not be fully allocated. Status of $SYSTEM.ZSYSSWAP.SWAP02 CPU 2 CPU Pages: Total 102305* Reserved 6361 Available 95944 Peak CPU Pages ever reserved 7280 Threshold 86959 CPU pages * Default swapfile extents may not be fully allocated. Status of $SYSTEM.ZSYSSWAP.SWAP03 CPU 3 CPU Pages: Total 102305* Reserved 5242 Available 97063 Peak CPU Pages ever reserved 6863 Threshold 86959 CPU pages * Default swapfile extents may not be fully allocated..
These specific SPRs must be installed on systems running G-series RVUs for compatibility and interoperability through a ServerNet Cluster with systems running J-Series RVUs. Table 15 Interoperability SPRs for G-Series RVU Systems Connected through ServerNet to J-Series RVU Systems Minimum SPR Product Name Description Introduced in this RVU T0294G08^AAX SNETMON Required for ServerNet clustering* G06.31 T0502G08^AAX SANMAN Required for ServerNet clustering* G06.
Table 17 SPRs for Software Migration and Software Management Operations Between G-Series, H-Series and J-Series RVU-Based Systems (continued) Minimum SPR Product Name Description Introduced in this RVU T9674D30^AAM PDTSHARE Required to recognize OCA region G06.27 T9276D30^AAW Axcel Required to recognize OCA region G06.27 T0448G06^AAA OCA Required to prepare TNS code files to run accelerated on a NonStop NS-series platform G06.
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 and NonStop Software Essentials to Install SPRs” (page 132).
* is not currently in a paused state, STARTSCM and DSM/SCM * server processes may hang indefinitely.
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.
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.
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.
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.
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. To build and apply the new software revision: 1.
3. 4. 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 5. Make a note of the new SYSnn.
10. 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.
============================================================================== ============================================================================== 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.
===========================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.
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.
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 and Planner Interface to Install SPRs” (page 139). 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 66).
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
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.
• 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.
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.
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.
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.
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.
3. 4. 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 5. 6. 7. Make a note of the new SYSnn.
9. (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 STATE ACTIVE FLAGS 3 , CPU 1 PRI 154 UNIT 4 DATA FILE %FULL $OPS0.SPL.DATA 4 10. 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.
11. 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). 12. Close the EMS Events, Status, and Request windows. 13. Exit the DSM/SCM Planner Interface. Print Operator Instructions From the Target Interface (ZPHITI) Print the operator instructions that you edited. 1.
(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.
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.
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.
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.
• 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.
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).
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 ................
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.
9 Loading This RVU This step loads this RVU into the memory of each processor. NOTE: For detailed information on 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.
Table 19 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
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. Alerts Before performing a system load: • Before halting the processors, stop applications that are still running, including TMF.
Failure to do this can result in an error during startup of OSS. This error occurs on systems with pre-T0585H01. B. When Upgrading From a J06.05 or Earlier 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 shown in this procedure, ensures the CLIM and host system will be compatible when you restart the system. For migrations from J06.05 or J06.
Steps for Loading the System A normal system load consists of loading the operating system from disk into the memory of processor 0 or processor 1 (this assumes the default location is the $SYSTEM volume): 1. In the OSM Low-Level Link, select Start System. The System Load dialog box appears. 2. a. From the Configuration drop-down menu under System Load Configuration, select a system load volume. You can select the $SYSTEM, FCDM-Load, CLIM-Attached-Load, or an alternate system volume. b.
The following example shows the same dialog box for a CLIM-attached load: 88 Loading This RVU
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.
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.
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.
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. Validate Your Core License For NB54000c and NB54000c-cg systems, use the OSM guided procedure Read Core License and verify that the license information is correct for your system.
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. From the ZDSMSCM 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.
/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. See product-specific documentation for more information on installation and configuration.
>FUP DUP $SYSTEM.ZTCPIP.SMPLPORT, $SYSTEM.ZTCPIP.PORTCONF >FUP DUP $SYSTEM.ZTCPIP.SMPLRESC, $SYSTEM.ZTCPIP.RESCONF >FUP DUP $SYSTEM.ZTCPIP.SMPLSERV, $SYSTEM.ZTCPIP.SERVICES Step 2: Check the PROTOCOL File (Optional) CAUTION: For both CIP and NonStop TCP/IPv6 (even if running in IPv4 mode), you must make sure that the PROTOCOL file contains ipv6 and icmpv6 entries.
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. Configure OSS See the Open System Services Management and Operations Guide and the Open System Services Installation Guide for information about updating and maintaining OSS database files.
Using OSS EasySetup (T0585) The OSS EasySetup product (T0585) is available for automated setup, as described in the Open System Services Installation Guide. OSS EasySetup is a series of TACL scripts that assist a site when configuring and installing a minimal OSS subsystem for the first time or when starting, stopping, or removing an OSS subsystem.
Re-deploy NonStop SOAP 4 If NonStop SOAP 4 was deployed and was being used with the previous RVU, the same SOAP 4 installation would not work after the RVU upgrade. To use NonStop SOAP 4 after an RVU upgrade, you must deploy the NonStop SOAP 4 version available with the new RVU in the existing NonStop SOAP 4 deployment directory, using the NonStop SOAP 4 deploy script.
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 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.
============================================================================== 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.
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.
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.
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.
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.
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. 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.
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.
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 39) 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.
5. install it from the CLIM DVD by following the procedure in the CLuster IO Protocols (CLIM) 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 by using either the CLIM Boot Service Configuration Wizard or the NonStop Maintenance LAN DHCP DNS Configuration Wizard, depending on which one you have installed on your NonStop system console.
c. Select Configure Boot Service on CLIM(s) and the appropriate option for whether or not there is a peer NonStop console installed. (If there is a peer, you are then prompted for the credentials of that peer console.) The next dialog box shows the IP addresses for the one or two CLIMs configured as BOOTP/DHCP servers. d. 110 Check the listed IP addresses to see if they correspond to the CLIMs you are downgrading. If the Hostname fields are empty, no CLIM is configured as a BOOTP server.
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.
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.
Click Yes. 2. In the iLO login window, log on. The default username is “Admin” and the password is hpnonstop. 3. On the Virtual Media tab, click Virtual Media Applet.
4. Only do this step if you receive the error: With Internet Explorer 7, you must enable the Java applet to use the Virtual Media. a. Go to the control panel, select Java, then select the advanced tab: Control panel 2 Java 3 Control panel dialog box for Java, Advanced tab Expand
5. This screen pops up, along with a warning. Click on the JavaScript screen to activate it, then click Yes in the warning box. 6.
a. In the Virtual CD/DVD-ROM area of the dialog box (1 in the following figure), select the image to which you want to reimage or downgrade (2 in the following figure). NOTE: If you do not have the correct image on the console, install the image from a CLIM Software DVD onto the console by following the procedures in the Cluster I/O Protocols (CIP) Configuration and Management Manual. Use this area (Virtual CD/DVD-ROM) of the applet screen. This is where you specify the local image file.
7. Navigate away from the applet window to the iLO window and select the System Status tab. Then under Last Used Remote Console, click the Launch button for Integrated Remote Console. 8. Select the Power Management Tab and press the Momentary Press button to power up the CLIM. On the pop up, click Yes.
1 2 3 Power management tab. Momentary press tab. Warning pop up. When the CLIM is shut off, the status shows Server is currently in STANDBY (OFF): 9. 118 Push Momentary Press again to restart the CLIM. The status now shows that the CLIM is on.
10. Return to the console window. 11. When the Debian splash screen appears, click within its window to activate it, and press Enter. Pressing Enter boots the CLIM: The boot takes a while. 12. When the final screen appears, do not click Continue until you have disconnected the Image File on the Virtual Media.
13. In the iLO browser screen, click on the Virtual Media tab, then press Virtual Media Applet. 14. In the Virtual CD/DVD-ROM area, click Disconnect.
15. Return to the remote console screen and press Enter to cause the program to continue. (Clicking Continue has no effect; you must press Enter.
After a brief pause during which the ProLiant window appears, a screen showing a successful installation like this appears: Prepare the CLIMs This procedure is necessary only if you reimaged a CLIM to revert CLIM software. 1. For each CLIM, set the IP address of eth0 through the iLO serial console. a. At the Linux prompt, log onto the CLIM. CLIMs are shipped with two default maintenance interface usernames and passwords: b.
In ABK and later versions of OSM Low-Level Link, the PCI Slot Configuration area has the groups of possible IP CLIM configurations selectable from a single drop-down menu. Sample ABK and Later Versions of OSM Low-Level Link, IP CLIM The PCI Slot Configuration area is disabled for Storage CLIMs in pre-ABK, ABK and post ABK versions of OSM Low-Level Link.
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.
4. 5. Click Yes. The CLIM reboots. If the system disk is a SAS disk and you have SAS disk enclosures that contain the system disks (both primary and mirror), issue the following command on one of the storage CLIMs that connect to the system disks: lunmgr ––approve yesall 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.
The ProLiant window shows briefly, and then the remote console window returns. Load the System A normal system load consists of loading the operating system from disk into the memory of processor 0 or processor 1: 1. In the OSM Low-Level Link, select Start System. The System Load dialog box appears. 2. In the System Load dialog box, select $SYSTEM or a saved configuration.
a. b. In the SYSnn field, enter nn, which is the number of the system subvolume that contains the version of the operating system you will load. Under SYSnn and CIIN Option, verify that the CIIN Disabled check box is unchecked. The CIIN file must be enabled because it contains commands needed to start the server. The startup TACL process performs the commands in the CIIN file and then logs off. For a description of the CIIN file, see the appropriate planning guide for your system. 3.
If the reload is initiated successfully, this message appears in a startup TACL window on the system console screen: PROCESSOR RELOAD: nn Complete CLIM Setup 1. Establish trust between the CLIM and the NonStop host system. Run SSOCLIM as any SUPER group user. 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 any SUPER group user. b. Enter SSOCLIM.
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.
d. e. 5. 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. 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.
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 applications, and connecting to a peer NSC from the NonStop Maintenance LAN DHCP DNS Configuration Wizard or the CLIM Boot Service Configuration Wizard.
A Using DSM/SCM and 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.
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.
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.
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.
> 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.
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.
Halt the Processors 1. 2. 3. 4. 5. 6. 7. 8. If necessary, log on to the OSM Low-Level Link application. 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. 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.
B Using DSM/SCM and 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.
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 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. At a TACL prompt, start SCF: 2> SCF 2. List the saved configuration files.
OSIMAGE 3. 0 57393152 05APR2008 8:56 255,255 NUNU 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.#CLCI Receive the SPR Into the DSM/SCM Archive Before Starting DSM/SCM Start TMF if it is not already running: > TMFCOM START TMF Bring the SPR Into the DSM/SCM Archive 1.
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.
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.
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.
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. 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.
C Installing SWID and DSM/SCM PVU Using NonStop Software Essentials Client Software NOTE: • You must install the DSM/SCM SPR and the SWID SPR from the RVU SUT and NonStop Software Essentials (T0895V02 AAA (client) or later and T0894V02 AAA (server) or later from Scout before you receive the RVU SUT. • Installing the destination-RVU SWID SPR at the same time you install new DSM/SCM and NonStop System Console server SPRs avoids a fingerprint or mismatched file problem.
To install the DSM/SCM client, see “Install the NonStop Software Essentials Client” (page 152). 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.*, E0894H02.*), VOL $DSMSCM, LISTALL where nnn is the RVU number (J06) and where $tape is the name of the tape drive containing this RVU.
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 and SWID SPRs 148 1. In the Configuration Revisions page, select the target system being upgraded and the current revision of the system being upgraded. Select New software revision.
3. 4. From the New software revision table, verify that the new version of DSM/SCM 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/12: DSM/SCM and SWID c.
NonStop Software Essentials runs the Build/Apply requests and displays a Status page that is automatically updated at regular intervals. 4. 5. 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 finished viewing, close the window.
Restart 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 DSM/SCM manually as described next. Before Starting DSM/SCM 1. Check that TMF is started: > TMFCOM STATUS TMF 2. 3.
manually or continue and IPM6031 will be run for you. Enter to continue or BREAK to exit. Verify that the Latest SPR of DSM/SCM is Installed To verify that the appropriate version of DSM/SCM is currently installed on your system, use the VPROC command to display the product version of TAEXE (Apply product of DSM/SCM) and CBEXE (Build product of DSM/SCM). At a TACL prompt, enter: > volume $dsmscm_vol.ZDSMSCM > vproc taexe > vproc cbexe The DSM/SCM version for this RVU is ACS.
D Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software 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.
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 NonStop Software Essentials Client” (page 152). 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.
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.
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.
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.
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.
> 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.
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.
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.
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 162 1. Using Windows Explorer, double-click Setup.exe.
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. (NonStop Software Essentials only supports shared product groups and HP recommends using shared product groups for PI as well.) 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.
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 160)), 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 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.
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.
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.
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.
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.
Index Symbols G $SYSTEM.ZTCPIP, 94 $SYSTEM.
Processor type in CONFTEXT file, 20 Profiles, target, changing information, 54, 67 PROTOCOL file configuration file location, 95 R RDF, 97 RELOAD command, 90, 127 Remote Database Facility, 97 S SCF testing the tape subsystem, 45 verifying critical processes, 44 verifying disks, 44 Scout for NonStop Servers, 14 ServerNet adapter firmware, 25 SERVICES file, 95 SMF, interoperability and configuration, 97 SOAP 4 see NonStop SOAP 4 Software revision, 19 Spooler backing up, command for, 80 checking status of co
