j06.14 software installation and upgrade guideh20628. · j06.14softwareinstallationandupgrade guide...
TRANSCRIPT
J06.14 Software Installation and UpgradeGuide
HP Part Number: 696596-001Published: August 2012Edition: J06.14 RVU only
© Copyright 2012
Legal Notice
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, CommercialComputer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government undervendor’s standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shallnot be liable for technical or editorial errors or omissions contained herein.
Export of the information contained in this publication may require authorization from the U.S. Department of Commerce.
Acknowledgements
Microsoft®, Windows®, Windows NT®, Windows® XP, and Windows Vista® are U.S. registered trademarks of Microsoft Corporation. Intel®
and Intel® Itanium® are trademarks of Intel Corporation in the U.S. and other countries. Java is a registered trademark of Oracle and/or its affiliates.
Java is a registered trademark of Oracle and/or its affiliates.
ContentsAbout This Document...................................................................................11
Supported RVUs.....................................................................................................................11Intended Audience..................................................................................................................11New and Changed Information in This Edition............................................................................11What This Guide Does Not Cover............................................................................................11Notation Conventions..............................................................................................................12
General Syntax Notation....................................................................................................12Related Information.................................................................................................................12Publishing History...................................................................................................................13HP Encourages Your Comments................................................................................................13
1 Overview of Installing This RVU..................................................................14SUT on DVD..........................................................................................................................14CLIM Software for This RVU.....................................................................................................14Disk Space Requirements.........................................................................................................14Operational Differences Between This RVU and H-series RVUs......................................................14Investigating a J-Series RVU......................................................................................................14System Console Requirements...................................................................................................15
Updating System Consoles (Optional)...................................................................................15Using OSM With This RVU......................................................................................................15
OSM Server-Based Components..........................................................................................15OSM Client-Based Components...........................................................................................16
Using DSM/SCM and NonStop Software Essentials With This RVU...............................................17NonStop Software Essentials and This RVU............................................................................17DSM/SCM and This RVU....................................................................................................17
OSBUILD SPR...............................................................................................................18DSM/SCM and Public DLLs.................................................................................................18DSM/SCM and OSS..........................................................................................................18Upgrading the NonStop Software Essentials Client.................................................................18Upgrading the DSM/SCM Client (Planner Interface) and the T6031H02 PVU............................19Summary of Software Installation Tasks.................................................................................19Check or Alter the CONFTEXT File Before Installing This RVU SUT ...........................................20
Installing CLIM Software..........................................................................................................20Backing Out the DSM/SCM Revision .......................................................................................20Managing Microcode and Firmware.........................................................................................21Installation, Migration, and Fallback..........................................................................................21
2 Managing Microcode and Firmware...........................................................22Managing BladeCluster Software and Firmware Requirements......................................................22Managing ME Firmware and ME FPGA Firmware.......................................................................22
Updating ME Firmware.......................................................................................................22Updating ME FPGA...........................................................................................................24
Managing OA Firmware for the c7000 Enclosure.......................................................................24Managing Server Blade Firmware.............................................................................................24Managing ServerNet Adapter Firmware....................................................................................25Managing SWAN and SWAN 2 Concentrator Firmware.............................................................28Managing NonStop Cluster Switch Firmware .............................................................................28Managing CLIM Firmware.......................................................................................................28Managing S-Series Interoperability Firmware..............................................................................29
3 Installation, Migration, and Fallback Considerations for This RVU....................30J06.04..................................................................................................................................30
Compiling C++ Programs to Run on RVUs Earlier Than J06.04.................................................30
Contents 3
SQL/MX Versioning Feature Removed..................................................................................30CLIM................................................................................................................................30
J06.05..................................................................................................................................31AF_UNIX Release 2 Migration and Fallback..........................................................................31
Migrating to AF_UNIX Release 2.....................................................................................31Falling Back to An Earlier Version of AF_UNIX..................................................................32
CLuster I/O Module (CLIM) Software Compatibility................................................................32J06.06..................................................................................................................................33
CLuster I/O Module (CLIM) Software Compatibility................................................................33DSM/SCM Upgrade Issues/Interoperability SPR Requirements.................................................33
J06.07..................................................................................................................................33Falling Back to iLO Firmware T0848AAA..............................................................................33DSM/SCM Upgrade Issues/Interoperability SPR Requirements.................................................34
J06.08..................................................................................................................................34NonStop SQL/MX.............................................................................................................34
J06.09..................................................................................................................................34SQL/MX 2.3.4 Requires JDBC T2 Driver...............................................................................34BladeCluster Solution Multi-Zone Support..............................................................................34
J06.10...................................................................................................................................34NonStop SOAP 4..............................................................................................................34New CLuster I/O Module (CLIM) Storage Devices..................................................................35Other CLIM and CIP Changes.............................................................................................35Hardware and Networking.................................................................................................35New Operating System Features .........................................................................................35TMF 3.6...........................................................................................................................35iTP WebServer 7.2.............................................................................................................35Expand Enhancements........................................................................................................35
J06.11...................................................................................................................................35Changes to SSOCLIM Privilege Requirement..........................................................................36
J06.12...................................................................................................................................36HP SUM...........................................................................................................................36
J06.13...................................................................................................................................36Safeguard.........................................................................................................................36Considerations Exist for Fallback to J06.11.............................................................................36Performance Tuning Requirements........................................................................................36Core License File................................................................................................................36Migrating a NonStop BladeSystem NB50000c to an NB54000c or NB50000c-cg to anNB54000c-cg ..................................................................................................................36Upgrading a NonStop BladeSystem NB54000c or NB54000c-cg to J06.13 or Later RVUs..........36HP NonStop Software Essentials..........................................................................................37IB CLIM Fallback Considerations..........................................................................................37EXTDECSL.........................................................................................................................37TNS/E ECOBOL................................................................................................................37
J06.14...................................................................................................................................37Halt and Hard Reset Processors When Upgrading to J06.14....................................................37SQL/MX Release 3.2.........................................................................................................37HP Power Regulator............................................................................................................37Safeguard.........................................................................................................................38
4 Upgrade Checklist....................................................................................39Required Information Checklists................................................................................................39Upgrade Checklist..................................................................................................................40
5 Preparing to Upgrade the Server Software (Preinstallation Tasks).....................44Back Up Important Files...........................................................................................................44
Back Up NonStop SQL/MP.................................................................................................44
4 Contents
Back Up NonStop SQL/MX files..........................................................................................44Back Up Spooler Control files..............................................................................................44Back Up TMF Files.............................................................................................................44Back Up CLIM Configuration Files........................................................................................44
Record the Current SYSnn........................................................................................................45Save the Current Configuration File (CONFxxyy)........................................................................45Verify System Processes...........................................................................................................46
Check Processor Status ......................................................................................................46Check System Components .................................................................................................46Verify the State of the Internal ServerNet Fabric......................................................................48Verify Firmware.................................................................................................................48Verify Critical System Processes............................................................................................49Verify Disk Drives...............................................................................................................49Verify Tape Drives (If Necessary)..........................................................................................50Verify That the CLIMs Are in the Started State........................................................................50Verify That the CIP Providers Are in the Started State...............................................................50Check the Status of the Spooler Collector..............................................................................51Check for Sufficient Swap File Space....................................................................................51
Install Node Interoperability SPRs..............................................................................................52Back Up System Information.....................................................................................................54For NonStop BladeSystem NB54000c and NB54000c-cg Ensure the Core License File is Ready forMigration..............................................................................................................................54Manually Install the NonStop Software Essentials Server Product...................................................54
6 Installing a SUT for This RVU Using NonStop Software Essentials....................55Alerts for Installing a SUT.........................................................................................................55Back Up Important Files...........................................................................................................55Receive New Software Into the Archive......................................................................................55Create a New Software Revision..............................................................................................58Build and Apply the New Software Revision...............................................................................61Print Operator Instructions From the Target Interface (ZPHITI).........................................................64Recovery for Problems Installing This RVU SUT or SPRs.................................................................66
Cancel Pending Build/Apply Requests..................................................................................667 Installing a SUT for This RVU Using the Planner Interface................................68
Alerts for Installing a SUT.........................................................................................................68Back Up Important Files...........................................................................................................68Receive New Software Into the Archive......................................................................................68Create a New Software Revision..............................................................................................72Build and Apply the New Software Revision...............................................................................75Print Operator Instructions From the Target Interface (ZPHITI).........................................................80Recovery for Problems Installing This RVU SUT or SPRs.................................................................83
Cancel Pending Build/Apply Requests..................................................................................838 Running ZPHIRNM ..................................................................................84
Alerts....................................................................................................................................84Back Up (Copy) Files in the $SYSTEM.ZTCPIP Subvolume (Best Practice).........................................84Stop Applications...................................................................................................................85Drain the Spooler (Optional)....................................................................................................85Back Up the Spooler Control Files.............................................................................................86ZPHIRNM..............................................................................................................................86
Using ZPHIRNM PREVIEW Mode.........................................................................................86Steps for Running ZPHIRNM................................................................................................87Verify That ZPHIRNM Ran Successfully..................................................................................88
9 Loading This RVU.....................................................................................89Alerts....................................................................................................................................91
Contents 5
Perform Updates.....................................................................................................................911. Before Halting the Processors...........................................................................................91
A. When Upgrading From a J06.04 or Earlier RVU: Removing #ZPLS..................................91B. When Upgrading From a J06.05 or Earlier RVU: CLIM Software.....................................92
2. Halt the Processors.........................................................................................................923. (Optional): Update System Firmware Using HP SUM...........................................................924. (Optional): Update HSS Firmware ...................................................................................925. (Required for Upgrade to J06.14) Reset the System Firmware................................................936. Upgrade the CLIM Software............................................................................................937. Loading the System.........................................................................................................93
Steps for Loading the System..........................................................................................93Completing the System Load (If Necessary).......................................................................96Verifying That the System Is Started..................................................................................96Updating Firmware (If Necessary)...................................................................................97
10 Resuming Normal Operations..................................................................98Revive the Down Half of the Mirrored Disk.................................................................................98Validate Your Core License.......................................................................................................98Start System Applications.........................................................................................................98
Before Starting DSM/SCM..................................................................................................98Initialize SQL for NonStop SQL/MP.................................................................................98Cold Start the Pathway Configuration...............................................................................99
Start DSM/SCM................................................................................................................99Run merge_whatis..................................................................................................................99Configure Specific Products (Post-System Load)..........................................................................100
Update NonStop TCP/IP Configuration Files........................................................................100Step 1: Copy the Sample TCP/IP Files Into $SYSTEM.ZTCPIP (Optional)..............................100Step 2: Check the PROTOCOL File (Optional).................................................................101Step 3: Optional: For Planner Interface, Ensure That PORTCONF and SERVICES Files AreComplete...................................................................................................................101
Configure OSS................................................................................................................102Install Specific OSS Files Using COPYOSS or PINSTALL....................................................102Run the inetd Process...................................................................................................102Using OSS Unautomated Configuration and Startup........................................................103Using OSS EasySetup (T0585)......................................................................................103
Configure SMF (Optional).................................................................................................103Configure the Remote Database Facility..............................................................................103Configure the WAN Manager...........................................................................................103Set Up iTP Webserver.......................................................................................................104Re-deploy NonStop SOAP 4..............................................................................................104
11 Backing Out the DSM/SCM Revision.......................................................105Products That Might Have Fallback Implications........................................................................105
Open System Services......................................................................................................105Storage Management Foundation .....................................................................................105
Before Backing Out the Revision.............................................................................................105Start the Target Interface (ZPHITI)............................................................................................105Submit a Backout Request......................................................................................................106Monitor the Backout Process Using NonStop Software Essentials.................................................109Monitor the Backout Process Using the Planner Interface............................................................110
12 Running ZPHIRNM to Reactivate the Previous Software Revision..................111Fallback Considerations for NonStop Software Essentials After ZPHIRNM....................................111Alerts..................................................................................................................................111Drain the Spooler (Optional)..................................................................................................111Run ZPHIRNM......................................................................................................................112
6 Contents
Using PREVIEW Mode......................................................................................................112Run ZPHIRNM.................................................................................................................112
13 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming NormalOperations ..............................................................................................114
Fallback Considerations for the Power Regulator.......................................................................114Alerts..................................................................................................................................114Task Overview.....................................................................................................................114Before Halting the Processors.................................................................................................115
(Optional) Prepare to Fall Back to Previous CLIM Firmware....................................................115Prepare to Fall Back to Previous CLIM Software....................................................................115When Falling Back to the J06.04 or Earlier RVU..................................................................118
Modify OSSINFIL........................................................................................................118If Using CLIMs for BOOTP, DHCP, or DNS Services..........................................................118
Halt the Processors................................................................................................................118While the Processors are Halted.............................................................................................119
(Optional) Fall Back to Previous CLIM Firmware....................................................................119Reimage the CLIMs..........................................................................................................119
Prepare the CLIMs................................................................................................................130Load the System...................................................................................................................133
Complete the System Load (If Necessary)............................................................................134Using the SSOCLIM * Option to Run SSOCLIM on All Available CLIMs........................................134Complete CLIM Setup............................................................................................................135Revert Firmware (If Necessary)................................................................................................138Install Specific OSS Files (If Necessary)....................................................................................138Verify That the System Is Started..............................................................................................138
A Using DSM/SCM and NonStop Software Essentials to Install SPRs................139Tools for Managing SPRs.......................................................................................................139
Scout for NonStop Servers................................................................................................139DSM/SCM.....................................................................................................................139SPRNOTES......................................................................................................................140
Install SPRs With DSM/SCM .................................................................................................140Save the Current Configuration..........................................................................................140Determine the Current SYSnn.............................................................................................140Receive the SPR Into the DSM/SCM Archive........................................................................141
Before Starting DSM/SCM...........................................................................................141Bring the SPR Into the DSM/SCM Archive.......................................................................141
Create a New Software Configuration That Includes the SPR..................................................141Build the New Revision.....................................................................................................142
Print Operator Instructions From the Target Interface (ZPHITI).......................................................142Run ZPHIRNM......................................................................................................................142If Running INSTALL^TEMPLATES Is Required.............................................................................143If a System Load Is Required...................................................................................................144
Halt the Processors ..........................................................................................................145Perform a System Load......................................................................................................145Start Your Applications and Processes.................................................................................145
B Using DSM/SCM and Planner Interface to Install SPRs.................................146Tools for Managing SPRs.......................................................................................................146
Scout for NonStop Servers................................................................................................146DSM/SCM.....................................................................................................................146SPRNOTES......................................................................................................................146
Install SPRs With DSM/SCM .................................................................................................147Save the Current Configuration..........................................................................................147Determine the Current SYSnn.............................................................................................147
Contents 7
Receive the SPR Into the DSM/SCM Archive........................................................................148Before Starting DSM/SCM...........................................................................................148Bring the SPR Into the DSM/SCM Archive.......................................................................148
Create a New Software Configuration That Includes the SPR..................................................148Build the New Revision.....................................................................................................149
Print Operator Instructions From the Target Interface (ZPHITI).......................................................149Run ZPHIRNM......................................................................................................................150If Running INSTALL^TEMPLATES Is Required.............................................................................150If a System Load Is Required...................................................................................................152
Halt the Processors ..........................................................................................................152Perform a System Load......................................................................................................152Start Your Applications and Processes.................................................................................152
C Installing SWID and DSM/SCM PVU Using NonStop Software Essentials ClientSoftware .................................................................................................153
Alerts..................................................................................................................................153Determine the Product Version of DSM/SCM on the Host System............................................153Determine the Latest SWID Product.....................................................................................153Determine the Product Version of DSM/SCM on the Client....................................................153
Copy (RESTORE) the H02 DSM/SCM Product Version to Disk (If Necessary).................................154Receive the H02 SWID and DSM/SCM SPRs ..........................................................................154Create a New Software Revision for H02 DSM/SCM and SWID SPRs ........................................155Build and Apply the DSM/SCM H02 Software Product Revision.................................................156Run the INSTALL^TEMPLATES Macro.......................................................................................157Restart Applications..............................................................................................................158
Before Starting DSM/SCM................................................................................................158Start DSM/SCM..............................................................................................................158Verify that the Latest SPR of DSM/SCM is Installed...............................................................159Verify That SWID Is Installed..............................................................................................159
Recovery for Problems While Installing the H02 Version of DSM/SCM .......................................159If NonStop Errors Are Displayed........................................................................................159
Cancel Pending Build/Apply Requests...........................................................................159Install the NonStop Software Essentials Client...........................................................................159
Determine the Product Version of NonStop Software Essentials on the Client............................159D Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software ..160
Alerts..................................................................................................................................160Determine the Product Version of DSM/SCM on the Host System............................................160Determine the Latest SWID Product.....................................................................................160Determine the Product Version of DSM/SCM on the Client....................................................160
Copy (RESTORE) the H02 DSM/SCM Product Version to Disk (If Necessary).................................161Receive the H02 SWID and DSM/SCM SPRs ..........................................................................161Create a New Software Revision for H02 DSM/SCM and SWID SPRs ........................................163Build and Apply the DSM/SCM H02 Software Product Revision.................................................163Rename the Applied DSM/SCM H02 Files By Running ZPHIRNM...............................................165Run the INSTALL^TEMPLATES Macro.......................................................................................165Restart Applications..............................................................................................................165
Before Starting DSM/SCM................................................................................................165Start DSM/SCM..............................................................................................................165Verify that the Correct SPR of DSM/SCM is Installed.............................................................166Verify That SWID Is Installed..............................................................................................166
Recovery for Problems While Installing the H02 Version of DSM/SCM .......................................166If NonStop Errors Are Displayed........................................................................................167
Cancel Pending Build/Apply Requests...........................................................................167Install the DSM/SCM Client From ZDSMSCM ..........................................................................167
Determine Your DSM/SCM Client Software Version..............................................................167
8 Contents
Determine the Current IP Address and Port Number..............................................................167Copy the ZDSMSCM Client File From the Host.....................................................................168Install the DSM/SCM Client Software.................................................................................169
E Updating SWAN Concentrator CLIP Firmware............................................174Acronyms.................................................................................................175Index.......................................................................................................177
Contents 9
Tables1 Tasks and Tools for Backing Out to the Previous SYSnn .........................................................212 Maintenance Entity (ME) Firmware File Names and Locations................................................233 Maintenance Entity (ME) FPGA File Names and Locations.....................................................244 Server Blade Firmware for NonStop BladeSystems and Blade Element for Nonstop NS2200
Series and NS2100 Systems..............................................................................................255 Blade Element Firmware for NonStop NS2000 Series Systems...............................................256 H-Series ServerNet Adapters File Names and Locations........................................................277 Updateable Firmware for the NonStop ServerNet Switch File Names and Locations..................288 Updateable Firmware for S-series Interoperability.................................................................299 NonStop SQL/MX and Supported RDF Versions..................................................................3410 Required Information Checklist, Before You Start ..................................................................3911 Information to Gather During the Upgrade (Checklist) ..........................................................4012 Upgrade Checklist...........................................................................................................4013 Interoperability SPRs for G-Series RVU Systems Connected Through Expand to H-Series or J-Series
RVU Systems...................................................................................................................5214 Interoperability SPRs for H-Series RVU Systems Connected through ServerNet to J-Series RVU
Systems .........................................................................................................................5215 Interoperability SPRs for G-Series RVU Systems Connected through ServerNet to J-Series RVU
Systems..........................................................................................................................5316 Interoperability SPRs for G-Series RVU Systems Connected through ServerNet to H-Series RVU
Systems..........................................................................................................................5317 SPRs for Software Migration and Software Management Operations Between G-Series, H-Series
and J-Series RVU-Based Systems.........................................................................................5318 System Load Paths in Order of Use for FCDM-Load...............................................................8919 System Load Paths in Order of Use for CLIM-Attached-Load....................................................90
About This DocumentThis guide describes:
• Upgrading the initial J06.14 RVU through the use of SUT refreshes, if necessary.
• Falling back to a previous SYSnn.
Supported RVUsThis manual supports the J06.14.00 RVU and all subsequent J06.14.nn RVUs unless otherwisenoted.
Intended AudienceThis guide is written for operations staff and support personnel and requires a working knowledgeof Windows Server 2003 or Windows Server 2008, OSM client and server components, systemconsole software, NonStop Software Essentials, DSM/SCM, Target Interface (ZPHITI), and ZPHIRNMapplications.
New and Changed Information in This EditionThis is a new edition.
What This Guide Does Not Cover• Changes from G-series RVUs. Differences between G-series and J-series RVUs are the same
as for H-series RVUs. For information on differences between G-series and H-series RVUs, seethe H06.nn Software Installation and Upgrade Guide.
• System migration planning. System-wide issues involved in migrating to the latest J-series RVUare covered in:
◦ The J06.nn Release Version Update Compendium for this RVU
◦ The Interactive Upgrade Guide 2 (IUG2)
• Installing a J-series RVU from a host system to a remote or separate network-connected targetsystem using an Expand connection or tape. See theNonStop Software Essentials User's Guideor the DSM/SCM User’s Guide for information on setting up target systems.
• Installing and configuring OSS.
• Upgrading HP NonStop System Console workstation applications. To install or upgrade HPand third-party system console client software, such as OSM client-based components, seethe NonStop System Console Installer Guide.
• Installing and configuring OSM server components. To install and configure OSM servercomponents, and start using client-based components, see the OSM Migration andConfiguration Guide.
• Installing, configuring, and migrating to HP NonStop SQL/MX. The SQL/MX Installation andManagement Guide provides step-by-step instructions for installing and configuring NonStopSQL/MX. Migrating a G-series NonStop SQL/MX or NonStop SQL/MP database to a J-seriesRVU and falling the database back to G-series RVUs is the same as for migrating to an H-seriesRVU. For information about migrating a G-series database, see the SQL Supplement for H-SeriesRVUs.
• Installing and configuring the IOAM enclosure and its components. See your HP serviceprovider.
Supported RVUs 11
Notation Conventions
General Syntax NotationThis list summarizes the notation conventions for syntax presentation in this manual.UPPERCASE LETTERS
Uppercase letters indicate keywords and reserved words. Type these items exactly as shown.Items not enclosed in brackets are required. For example:MAXATTACH
Italic Letters
Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed inbrackets are required. For example:file-name
Computer Type
Computer type letters indicate:• C and Open System Services (OSS) keywords, commands, and reserved words. Type
these items exactly as shown. Items not enclosed in brackets are required. For example:Use the cextdecs.h header file.
• Text displayed by the computer. For example:Last Logon: 14 May 2006, 08:02:23
• A listing of computer code. For exampleif (listen(sock, 1) < 0){perror("Listen Error");exit(-1);}
Bold Text
Bold text in an example indicates user input typed at the terminal. For example:
ENTER RUN CODE
?123CODE RECEIVED: 123.00
The user must press the Return key after typing the input.
Related InformationNOTE: Many of the documents referenced in this guide are located in the NTL, which has movedto the HP Business Support Center (BSC) at http://www.hp.com/go/nonstop-docs. See Tips forLocating NonStop Documents in the BSC for information about locating NonStop documents.
• The CLuster I/O Module (CLIM) Software Compatibility Reference provides the compatibilityinformation of CLIM DVD SPRs and host RVUs.
• The NonStop Firmware Matrices provides the firmware levels required for this RVU.
• The NonStop System Console Installer Guide contains information on installing OSMclient-based components, and other applications on system consoles.
• The J06.nn Release Version Update Compendium for this RVU provides summary informationon the new features and migration issues.
• The comForte MR-Win6530 online help provides information on configuring MR-Win6530sessions.
12
• The Support and Service library and guided procedures provide online help and web-basedinstructions for performing many tasks, including updating firmware. The Support and Servicelibrary is available in the NonStop Technical Library (NTL).
• The NonStop Software Essentials User's Guide provides detailed, task-oriented instructionsfor using NonStop Software Essentials. TheDSM/SCM User's Guide provides detailed,task-oriented instructions for using DSM/SCM to perform the various tasks associated withinstalling and managing software revisions.
• For information about planning and configuring the installation of NonStop systems, see theplanning guide for your system.
• The NonStop Operations Guide provides information for operating and maintaining theNonStop BladeSystem server.
• For detailed instructions and checklists for installing a NonStop system, see the hardwareinstallation manual for your system.
• The OSM Migration and Configuration Guide provides an overview of all OSM applicationsand components, how to configure and get started with OSM, and how to use the primaryOSM interface, OSM Service Connection, to monitor and perform actions on system andcluster resources.
Publishing History
Publication DateProduct VersionPart Number
August 2012N.A.696596–001
HP Encourages Your CommentsHP encourages your comments concerning this document. We are committed to providingdocumentation that meets your needs. Send any errors found, suggestions for improvement, orcompliments to [email protected] the document title, part number, and any comment, error found, or suggestion forimprovement you have concerning this document.
Publishing History 13
1 Overview of Installing This RVUFor information on installing SPRs, see Appendix A (page 139).
SUT on DVDThe J-series SUT is also available on DVD. For instructions on installing the SUT from the DVD, seethe IPSetup User’s Guide.
WARNING! See the Support Note S12017 (IPSetup on 64-bit Windows causes IE problems) forinformation about preventing or recovering from an Internet Explorer issue that can occur on 64-bitWindows operating systems.
CLIM Software for This RVUIf your system has CLIMs installed, the CLIM software is available on a separate DVD and in Scoutfor NonStop Servers. Before installing CLIM software on your NonStop system, you must install thesoftware on the system console as described in the Cluster I/O Protocols (CIP) Configuration andManagement Manual.CLIM software compatibility across RVUs is documented in the CLuster I/O Module (CLIM) SoftwareCompatibility Reference.
Disk Space RequirementsThe maximum SUT with all standard products, plus all optional products available to customers,contains approximately 8 gigabytes (GB) of data, depending on optional products (however,actual disk space required can be much greater).
Operational Differences Between This RVU and H-series RVUsThere are no known operational differences between H-series and J-series RVUs. Operationaldifferences between G-series and J-series RVUs are the same as for G-series and H-series; for thatinformation, see the H06.nn Software Installation and Upgrade Guide.
Investigating a J-Series RVUSeveral resources are available to help you plan for installing a J-series RVU:
• Product softdocs and the README file.
• The J06.nn Release Version Update Compendium provides highlights of the new products andfeatures for each H-series RVU. It also discusses the effect these changes have on installationand configuration, operations and management, data files, applications, and networks.
• The IUG2 simplifies the planning of software and hardware for J-series RVUs. Select theproducts and RVUs you use, and the Interactive Upgrade Guide 2 automatically displayscustomized migration instructions and lists new features.
• The Managing Software Changes manual explains TRM2000 and provides information aboutsystem migration and installation processes, SPR analysis, and resources for investigating newRVUs and SPRs.
• Scout for NonStop Servers is a Web-based SPR analysis and delivery tool. You can accessScout through HP NonStop eServices Portal at:https://onepoint.nonstop.compaq.com/buildpage.asp.
14 Overview of Installing This RVU
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 softdocsand release documents on the SUT after you receive new software into the archive. For moreinformation, see the DSM/SCM User's Guide or Scout.
System Console RequirementsA system console is an HP-approved personal computer used to run maintenance and diagnosticsoftware for NonStop servers. See the NonStop System Console Installer Guide to find out whichoperating system new consoles are configured to use.
Updating System Consoles (Optional)HP recommends that you always update to the latest NSC installer DVD. If you have ordered newsystem consoles for this RVU, the latest client-side software is already installed; if not, obtain thelatest NSC installer DVD. See the NonStop System Console Installer Guide for detailed informationon installing the system console software. If you have NonStop Software Essentials installed on adifferent HP SIM CMS, update it there.If you are migrating a G-series legacy system console to use OSM, certain client-side systemrequirements must be met. See the NonStop System Console Installer Guide and the OSMMigrationand Configuration Guide for PC system requirements and information on migrating to OSM.See the NonStop System Console Installer Guide for instructions on upgrading your system consolesoftware to the latest available versions.This guide shows you how to upgrade the RVU using either the DSM/SCM Planner Interface orNonStop Software Essentials. If you are using a 64-bit console, you must use NonStop ServerEssentials. If the NonStop Server Essentials server is not installed, see the NonStop SoftwareEssentials Installation and Quick Start Guide for installation procedures.
Using OSM With This RVU
OSM Server-Based ComponentsThe server-based OSM SPR released with this RVU is T0682H02^ACZ. This version may besuperseded by a later version.
NOTE: Beginning with T0682H02^AAZ, the OSM Service Connection Suite requires you toinstall JRE version 1.5.0_11 or later. However, these JRE versions are incompatible with OSMserver versions older than T0682H02^AAY (for NonStop NS series servers and BladeSystems)and T0682H02^AAV (for NonStop S-series servers). Therefore, all NonStop servers also managedby this console must be running one of those OSM server versions or later.
Highlights of OSM support include:
• Guided or documented service procedures for replacing various system components in NonStopBladeSystems, NS2000 series, NS2100, and NS2200 series servers.
• Firmware updates for:
c7000 enclosure firmware◦◦ Blade element firmware for NS2000 series, NS2100, and NS2200 series servers
◦ VIO enclosure firmware
◦ ME firmware on ServerNet Switch Boards, located in IOAMs, VIO logic boards, andc7000 enclosures
◦ FCSA
System Console Requirements 15
◦ 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.
◦ Test incident report delivery paths for HP Insight Remote Support Advanced
• Support for using HP SIM to help monitor your NonStop systems, and SSL, which is requiredfor HP SIM support. To install HP SIM, see the NonStop System Console Installer Guide. Toenable SSL, see the OSM Migration and Configuration Guide.
For more information about configuring and getting started with OSM, see the OSM Migrationand Configuration Guide.For more information about using the OSM Service Connection, see the OSM Service ConnectionUser's Guide.
OSM Client-Based ComponentsOSM client-based component upgrades are delivered on the NonStop System Console InstallerDVD. HP recommends upgrading to the very latest console software available.The OSM client-based products are:
• OSM Low-Level Link, which is used to provide down-system support, allowing you tocommunicate with your HP NonStop server even when the NonStop Kernel operating systemis not running. In addition to performing the system loads, it is used to configure VIO andother modules, configure CLIMs, and update CLIM software. For information on other featuresand functionality, see the OSM Low-Level Link online help.
• OSM Console Tools, which includes these products:
OSM System Inventory Tool◦◦ Terminal Emulator File Converter
◦ OSM Certificate Tool
◦ NonStop Maintenance LAN DHCP DNS Configuration Wizard (replaces the CLIM BootService Configuration Wizard on NonStop System Console Installer DVD, Update 17and later)
◦ Down System CLIM Firmware Update Tool
◦ DHCP DNS Configuration Wizard
For more information, see the NonStop System Console Installer Guide.
16 Overview of Installing This RVU
NOTE: The OSM Notification Director has been removed from the NSC DVD; it will not functionon consoles running Windows 2008 Server. Its functionality has been replaced by HP InsightRemote Support Advanced. For more information, see "Insight Remote Support Advanced forNonStop," in the NonStop Technical Library.For more information on OSM client applications, see the OSM Migration and ConfigurationGuide or the online help available from within each application. To upgrade an existing systemconsole to the latest console software, see the NonStop System Console Installer Guide
OSM Low-Level Link highlights include:
• A System Load dialog box provides the ability to:
Load the system from an alternate system load configuration that was previously savedon the system console. After a configuration is saved, you can load the system usingmirrored disks without reviving.
◦
◦ Save a system configuration on the system console for future use.
• Configure Module action, used to configure IOAM and VIO modules.
• Configure CLIMs and update CLIM software.For more information on OSM client applications, see the OSM Migration and ConfigurationGuide or the online help available from within each application. To upgrade an existing systemconsole to the latest console software, see the NonStop System Console Installer Guide.
Using DSM/SCM and NonStop Software Essentials With This RVU
NonStop Software Essentials and This RVUThe HP NonStop Software Essentials product is a software installation and management tool forNonStop servers. NonStop Software Essentials uses DSM/SCM server software and provides areplacement for DSM/SCM Planner Interface functions as well as certain Host Maintenance Interfacefunctions that is more secure, easier to use, and overcomes other shortcomings of DSM/SCM. Itcoexists with DSM/SCM; you can use either NonStop Software Essentials or the DSM/SCM PlannerInterface for tasks in which there is overlapping functionality. For more information, see the NonStopSoftware Essentials Installation and Quick Start Guide and the NonStop Software Essentials User'sGuide.NonStop Software Essentials is first released in J06.13 and available by SPRs for all pre-J06.13RVUs.
DSM/SCM and This RVU• The DSM/SCM H02 PVU (T6031H02) is supported.
• A new type of hardware platform and selectable option, TNS/E, has been added to thePlanner Interface screens. See the DSM/SCM User’s Guide for configuration information.
• By default, the DSM/SCM H02 PVU is configured to manage OSS files. Check that OSS isconfigured and started if DSM/SCM is set to manage OSS files. If not, the Apply can fail.
• CNFGINFO supports system generation options for DLLs.
• Creating a SIT is not supported in J-series RVUs.
• You might need to update both the client and server-side SPRs. For this RVU, the PlannerInterface screen displays G02/H02 for the client side and H02 for the server side.
Using DSM/SCM and NonStop Software Essentials With This RVU 17
• 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 theSWID 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.03 or later host system is used to perform DSM/SCM builds for a targetsystem that is running an H-series release prior to H06.12, you must include the appropriate T0431(OSBUILD) SPR for that target system before performing the build. If this is not done, then theDSM/SCM Sysgen (OSBUILD) will fail. The build will complete successfully if it is being done foran H06.12 or later system.The appropriate T0431 SPRs are:
Target NonStop System RVUSPR
H06.10 and H06.11T0431H01^AAK
H06.09T0431H01^AAH
H06.08T0431H01^AAN
H06.07T0431H01^AAM
H06.05 and H06.06T0431H01^AAL
Any J-series RVU attempting to build an H-series RVU prior to H06.12 must install these SPRs.
DSM/SCM and Public DLLsDSM/SCM manages and controls the distribution, installation, and activation of public DLLs inJ-series RVUs the same way that it does in H-series RVUs. Public DLLs are installed on the H-seriesand J-series target systems in their own subvolume.To manage OSS files in J-series RVUs, use the T6031H01 or later SPR. The corresponding clientversion, Planner Interface, or NonStop Software Essentials must also be installed. For this RVU, theSPR for the client is T0895V02 for NonStop Essentials and T6031G02/H02 for the PlannerInterface. The DSM/SCM SPR for the server side is T6031G02/H02. The SPR for the NonStopSoftware Essentials server is T90894H02 AAA and for the PI server is T6031H02.
DSM/SCM and OSSWhen performing a Build/Apply, ensure that the setting of the Manage OSS Files optionmatches with your target system. If the target system is not to use OSS, you must uncheck the OSSfiles option box before beginning a Build request. If the box is left checked, OSS is included bythe Build request. The OSS root fileset needs to be configured and started before files can becopied into the OSS file system by DSM/SCM. For OSS users who request HP to install OSS, it isassumed that OSS is installed and configured. However, the OSS root fileset ($ZPNS) must be inthe started state; otherwise, the Build/Apply fails.
Upgrading the NonStop Software Essentials ClientYou can now order 64-bit consoles, which require NonStop Software Essentials. (NonStop SoftwareEssentials is pre-installed on the 64-bit consoles. See the NonStop Software Essentials Installation
18 Overview of Installing This RVU
and Quick Start Guide for how to install it.) If you did not order new system consoles, downloadHP SIM and NonStop Software Essentials from Scout:• T0895 V02 AAA (Windows)
• T0996 V02 AAA (Linux)Downloads for HP SIM are here: www.hp.com/go/hpsim.For instructions on installing NonStop Software Essentials, see the NonStop Software EssentialsInstallation and Quick Start Guide.
Upgrading the DSM/SCM Client (Planner Interface) and the T6031H02 PVUTo upgrade the DSM/SCM client, if you did not order new system consoles, the DSM/SCM clientversion must be downloaded from the ZDSMSCM subvolume. (If you have acquired new systemconsoles, the most up-to-date DSM/SCM client is already installed.) To download the client version(Planner Interface) from ZDSMSCM to a separate PC console or your current console, follow theclient or Planner Interface installation instructions in the DSM/SCM User’s Guide or “InstallingSWID and DSM/SCM PVU Using NonStop Software Essentials Client Software ” (page 153).
Summary of Software Installation TasksTo 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.Each time a new version of a product is received, only changed files are placed in the Archive,and file attributes are updated in the host database.
2. Create a new software revision.A software revision is a list of products stored in the DSM/SCM Archive that will be built intoa new software revision. A software revision can include a SUT, SPRs, and third-party software.When you create a new software revision, DSM/SCM selects the products in the SUT thatare licensed for your site and replaces previous versions of the products.
3. Build and apply the new software configuration revision.The Build process creates an activation package containing all the products listed in the newsoftware revision. During the Apply process, the activation package is transferred to the targetsystem, and the new software is placed on the target system’s subvolumes. When the Applyrequest is finished, a snapshot is automatically created and returned to the host, ifExpand-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 currentlyrunning programs. You run the ZPHIRNM program on the target system to:
• Rename the files that currently have actual file names to fabricated names. These filesbecome obsolete when the new files are renamed.
• Rename the new files, which have fabricated names, to their actual names.After ZPHIRNM has completed renaming all OSS and Guardian files, it will run ZMODGPif it exists in the SYSnn being activated and if:
◦ The configuration being activated contains a ZCNFDEFS TSV
◦ One or more of the ZcccGP files in the ZCNFDEFS TSV are new or changed (ascompared to the last configuration activated).If no ZcccGP files change, ZMODGP is not run.
Using DSM/SCM and NonStop Software Essentials With This RVU 19
ZMODGP is a TACL script that makes changes to the generic-process definitions inthe system configuration database. When you use the ZMODGP script, you do notneed to hard code new generic process definitions directly into the $ZCDB process(T6586, Configuration Services).
Check or Alter the CONFTEXT File Before Installing This RVU SUT
NOTE: Tape_Label_Processing is controlled by the Storage Subsystem ($ZZSTO) ALTER SUBSYScommand. The CONFTEXT file directive TAPE_LABEL_PROCESSING gets overridden by the StorageSubsystem settings. See the SCF Reference Manual for the Storage Subsystem for more informationabout the ALTER SUBSYS command.
The processor type (SYSTEM_PROCESSOR_TYPE) is specified in the CONFTEXT file. It currentlyhas only one value:
SYSTEM_PROCESSOR_TYPESystem
NSE-MNB50000c, NB50000c-cg,NB54000c, NB54000c-cg, NS2200series, NS2100, and NS2000 Series
Check the CONFTEXT file to ensure that the following entries are present. They are needed for theimplicit DLLs:
SYSTEM_IMPLICIT_INIT_FILES TANDEM^IMPLICIT^INIT^FILES;SYSTEM_IMPLICIT_CORE_FILES TANDEM^IMPLICIT^CORE^FILES;SYSTEM_IMPLICIT_FS_FILES TANDEM^IMPLICIT^FS^FILES;SYSTEM_IMPLICIT_MCP_FILES TANDEM^IMPLICIT^MCP^FILES;SYSTEM_IMPLICIT_ETC_FILES TANDEM^IMPLICIT^ETC^FILES;
This example shows a CONFTEXT file:
$TEMP CONFIGXX 2> type conftextALLPROCESSORS: SYSTEM_PROCESSOR_TYPE NSE-M; SYSTEM_VOLUME_SUBVOL $SYSTEM.SYS00; SYSTEM_LIBRARY_CODE_FILES TANDEM^LIBRARY^CODE^FILES; SYSTEM_PROCESS_CODE_FILES TANDEM^PROCESS^CODE^FILES; SYSTEM_PROCESS_LIBRARY_FILES TANDEM^PROCESS^LIBRARY^FILES; STANDARD_MICROCODE TANDEM^STANDARD^MICROCODE; MICROCODE_FILES TANDEM^MICROCODE^FILES; FILES_TO_COPY_TO_NEW_SYSTEM TANDEM^FILES^TO^COPY; SYSTEM_IMPLICIT_INIT_FILES TANDEM^IMPLICIT^INIT^FILES; SYSTEM_IMPLICIT_CORE_FILES TANDEM^IMPLICIT^CORE^FILES; SYSTEM_IMPLICIT_FS_FILES TANDEM^IMPLICIT^FS^FILES; SYSTEM_IMPLICIT_MCP_FILES TANDEM^IMPLICIT^MCP^FILES; SYSTEM_IMPLICIT_ETC_FILES TANDEM^IMPLICIT^ETC^FILES; FORMATTER_TEMPLATE_FILES TANDEM^FORMATTER^TEMPLATE^FILES; INITIAL_COMINT_INFILE $DSMSCM.SYS.CIIN;
Installing CLIM SoftwareIf your NonStop system has CLIMs installed, you must upgrade the CLIM software prior to coldloading the SUT. The procedure for upgrading CLIM software is described in the Cluster I/OProtocols (CIP) Configuration and Management Manual.
Backing Out the DSM/SCM RevisionIf you encounter a problem with a SUT refresh that cannot be resolved, you can back out theDSM/SCM revision.
20 Overview of Installing This RVU
Table 1 Tasks and Tools for Backing Out to the Previous SYSnn
Documented in This Chapter...Use This Tool...To Perform This Task...
“Backing Out the DSM/SCM Revision ”(page 20)
DSM/SCM Target Interface (ZPHITI)1. Submit a backout request.
Chapter 12: “Running ZPHIRNM toReactivate the Previous SoftwareRevision”
DSM/SCM ZPHIRNM program2. Reactivate the previous softwarerevision.
“Falling Back on the CLIMs, Loading thePrevious RVU, and Resuming NormalOperations ” (page 114)
OSM Low-Level Link3. Load the HP NonStop operatingsystem and, if CLIMs are installed,load the CLIM software from theprevious revision into the firstprocessor.
“Falling Back on the CLIMs, Loading thePrevious RVU, and Resuming NormalOperations ” (page 114)
TACL RELOAD command4. Reload the remaining processors.
Managing Microcode and FirmwareWhen you install a new RVU, you must ensure you are running the current firmware and microcodeversions and upgrade those products, if necessary. The current firmware versions and upgradeprocedures are given in Chapter 2: “Managing Microcode and Firmware”
Installation, Migration, and FallbackMany products have special considerations for installation, migration, and fallback, which youshould be aware of before installing the new RVU. These considerations are described in Chapter 3:“Installation, Migration, and Fallback Considerations for This RVU”.
Managing Microcode and Firmware 21
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 compatibleversions are installed. Failure to do so can result in a wide range of system problems, fromintermittent faults to partial or complete system outages. Carefully review the NonStop FirmwareMatrices document, located in the Service Information section of the Support and Service collectionof the NonStop Technical Library at www.hp.com/go/nonstop-docs.
NOTE: On NonStop NS2200 series, NS2100, and NonStop BladeSystem NB54000c andNB54000c–cg servers, firmware can be updated using HP SUM. (See the NonStop FirmwareMatrices for the link and for information about required levels
OSM displays firmware version information, including file names and a Compare State attribute,which compares the current version against the default or available version. Outside of OSM, youcan use the FILEINFO command to see firmware files.Enter this FILEINFO command, if your Carrier Grade system is connected to a NonStop S-seriesserver, to check for location and file information for CPUCODE and SPCODE:$SYSTEM STARTUP 7> FILEINFO $SYSTEM.SYS*.*CODE*
Enter this FILEINFO command to check for location and file information for the HSS firmware:$SYSTEM STARTUP 7> FILEINFO $SYSTEM.SYS*.*FIRM*
Enter this FILEINFO command to check for location and file information for other firmware, suchas ServerNet Clustering:$SYSTEM STARTUP 7> FILEINFO $SYSTEM.SYS??.M????
Managing BladeCluster Software and Firmware RequirementsThe software and firmware required for NonStop BladeClusters is included in this RVU. For moreinformation, see the BladeCluster Solution Manual.
Managing ME Firmware and ME FPGA FirmwareThere is ME firmware and ME FPGA firmware on the ServerNet switches located in c7000enclosures, on VIO logic boards, and (optionally) in IOAMs.For systems with IOAMs, the ME firmware and ME FPGA should be the same for all IOAMs. MEfirmware and ME FPGA can be checked and, if necessary, updated from either the OSM Serviceconnection or the Low-Level Link.For systems with VIO enclosures, all enclosures in a system should have consistent versions. MEfirmware and ME FPGA can be checked and, if necessary, updated from either the OSM Serviceconnection or the Low-Level Link.For information on using OSM Low-Level Link to perform ME firmware updates, see the online helpavailable within the application.If you have legacy NonStop S-series enclosures attached to your system, you will also have SPfirmware to check. For more information on updating SP firmware, see the current G06.nn SoftwareInstallation and Upgrade Guide .
Updating ME Firmware
NOTE: For product levels, see the NonStop Firmware Matrices document.
22 Managing Microcode and Firmware
Table 2 Maintenance Entity (ME) Firmware File Names and Locations
Default LocationFile NameComponentFirmware Name
SYSnn subvolumeM2805ServerNet Switch (IOAMenclosure)
ME firmware (see Cautionbelow)
SYSnn subvolumeM4805ServerNet Switch (c7000enclosure)
Blade ME firmware (seeCaution below)
SYSnn subvolumeM1805VIO enclosure logic boardME firmware for IME inVIO enclosures (seeCaution below)
For more information on managing ME firmware, see:• The planning guide or hardware installation manual for your system.
• The online help in the OSM Low-Level Link or Service Connection.
CAUTION: You should not use the Multi-Resource Actions dialog (in the OSM Service Connection)to update ME FW simultaneously on both fabrics, or a system outage might occur.
Updating ME Firmware on an I/O Adapter Module (IOAM)There is ME firmware on the ServerNet Switch Board object in each IOAM of NonStopBladeSystems.
NOTE: In the OSM Low-Level Link, a ServerNet Switch Board is represented as an ME object.
To use the OSM Service Connection to update the ME firmware for IOAMs:1. Locate the ServerNet Switch Board on one Internal ServerNet Fabric: Select System > Group
> IOAM Enclosure > IOAM > ServerNet Switch Board.2. Right-click the ServerNet Switch Board object and select Actions.3. In the Actions dialog box, select ME Firmware Update and click Perform Action.4. Monitor the update.5. Repeat for the IOAM switch on the other Internal ServerNet Fabric.
Updating ME Firmware on a c7000 EnclosureThere is maintenance entity (ME) firmware on the ServerNet Switches within the c7000 enclosuresof NonStop BladeSystems.
NOTE: In the OSM Low-Level Link, a ServerNet Switch is represented as an ME object.
To use the OSM Service Connection to update the ME firmware for the ServerNet Switches:1. Locate the ServerNet Switch on one Internal ServerNet Fabric: Select System > Enclosure 100
> ServerNet Switch. The switches are labeled 100.2.5 and 100.3.7. You can select eitherswitch.
2. Right-click the ServerNet Switch object and select Actions.3. In the Actions dialog box, select ME Firmware Update and click Perform Action.4. Monitor the update.5. Repeat for the other ServerNet Switch.6. 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.)
Updating ME Firmware on a VIO EnclosureThere is ME firmware on the VIO Logic Board object in each VIO enclosure.
NOTE: In the OSM Low-Level Link, a VIO logic board is represented as an IME object.
Managing ME Firmware and ME FPGA Firmware 23
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
• System > Group nnn > VIO Module > VIO Logic Board2. Right-click the VIO Logic Board object and select Actions.3. In the Actions dialog box, select ME Firmware Update and click Perform Action.4. Monitor the update.5. Repeat for the VIO enclosure in the other fabric.
Updating ME FPGA
NOTE: For firmware levels, see the NonStop Firmware Matrices document, located in the ServiceInformation section of the Support and Service collection of the NonStop Technical Library atwww.hp.com/go/nonstop-docs.
Table 3 Maintenance Entity (ME) FPGA File Names and Locations
Default LocationFile NameComponentFirmware Name
SYSnnSAM0815ServerNet Switch (c7000enclosure)
ME FPGA (see Cautionbelow)
SYSnnSAM0437ServerNet Switch (IOAMenclosure)
ME FPGA (see Cautionbelow)
SYSnnSAM0789VIO enclosure logic boardME FPGA for IME in VIOenclosures (see Cautionbelow)
CAUTION: You should not use the Multi-Resource Actions dialog (in the OSM Service Connection)to update ME FPGA simultaneously on both fabrics, or a system outage might occur.
Use the OSM Service Connection to check and (if necessary) update the ME FPGA for all c7000enclosures and IOAMs just as you did when updating ME firmware, but choose the ME FPGAUpdate action instead.For information on using the OSM Low-Level Link to update ME FPGA, see the online help availablewithin the application.
Managing OA Firmware for the c7000 EnclosureCheck the NonStop Firmware Matrices document for the minimum supported OA firmware forthis release.
Managing Server Blade FirmwareNOTE: For minimum firmware levels for this RVU, see the NonStop Firmware Matrices document.
24 Managing Microcode and Firmware
Table 4 Server Blade Firmware for NonStop BladeSystems and Blade Element for Nonstop NS2200Series and NS2100 Systems
Product DescriptionFirmware Name
Used to reset, halt, load, and dump a server blade. Delivered as anIndependent Product on the NSC DVD.
Halted State Services firmware
Controller firmware for legacy I/O or SCSI disks in G-series RVUs.ISP1040 firmware
Used during a system load.DISKBOOT firmware
Table 5 Blade Element Firmware for NonStop NS2000 Series Systems
Product DescriptionFirmware Name
Used to reset, halt, load, and dump a Server blade. Delivered as anIndependent Product on the NSC DVD.
Halted State Services and HPI Loader T8004Firmware
Controller firmware for legacy I/O or SCSI disks in G-series RVUs.This firmware is packaged as part of the DVD containing T8004 andcannot be updated independently.
ISP1040 Firmware
Used during a system load. This firmware is packaged as part of theDVD containing T8004 and cannot be updated independently.
DISKBOOT Firmware
The installation procedure for blade element firmware is described in the Updating Blade ElementFirmware in an NS2200 Series, NS2100, NS2000 Series, NS1200 or NS1000 Server serviceprocedure.
Managing ServerNet Adapter FirmwareThis manual covers only the ServerNet adapters supported on H06.14 and later RVUs:
• FCSA
• G4SA
• TRSA
• CCSATo update firmware for ServerNet adapters connected to legacy IOMF2 CRUs, see the latestG-series Software Installation and Upgrade Guide.
NOTE: Before connecting your system to a NonStop S-series system through legacy I/O, youmust first update the firmware for both the S-series G4SA and the FCSA. Firmware for both theG4SA and FCSA adapters used for S-series systems is not initially compatible with NonStopBladeSystems.If you have a NonStop S-series system that is connected to your system through Expand or ServerNetClusters, you do not need to initialize the G4SA or FCSA firmware.To find out if your system supports connectivity to NonStop S-series systems, see the planning guidefor your system.
To see if the ServerNet adapter firmware needs to be updated, navigate down the OSM tree panefor FCSA, G4SA and TRSA:
CAUTION: Ensure that the system is running the new RVU before starting this procedure.
Managing ServerNet Adapter Firmware 25
• 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 firmwarelocated in the FCSA FLASH memory. The boot firmware runs on every FCSA after poweron and after hardware or firmware errors, and is re-downloaded to initialize the adapterand to accept downloaded firmware from the processor. The AAN SPR is available forthis T number.
◦ The flash firmware (T0612G06) contains version information about the operationalfirmware located in the FCSA FLASH memory. Flash firmware runs the FCSAs used forsystem load so that the processor boot millicode can read the system-load disk.
◦ RAM firmware: Operational firmware is downloaded to the FCSA when you issue thefirst START DISK command to the first disk drive in the fibre-channel loop.
◦ Use the OSM Service Connection to check the FCSA’s firmware version and update thefirmware, if needed. If the Compare State shows Down-rev, update the firmware. Thefollowing example shows that the firmware is at an earlier version and needs to beupdated:
26 Managing Microcode and Firmware
• G4SA. The OSM Service Connection displays G4SA firmware attributes and action underthe 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 firmwareattributes show that the current firmware Version is the same as the available Default FileVersion; no update is necessary. If the Compare State was Down-rev, you would use theFirmware Update action to update the firmware:
For information on updating firmware, see the OSM online help on the OSM Multi-Resource Actiondialog box.
NOTE: Firmware levels for each component are located in the NonStop Firmware Matricesdocument.
Table 6 H-Series ServerNet Adapters File Names and Locations
ToolDefault LocationFile NameComponentFirmware Name
Fibre ChannelServerNet Adapter
OSM ServiceConnection orSCF
SYSnn subvolumeI0630FCSAFCSA Flashfirmware
(FCSA) Installationand Support Guide
Fibre ChannelServerNet Adapter
OSM ServiceConnection orSCF
SYSnn subvolumeC0612R00FCSAFCSA Flash Bootfirmware
(FCSA) Installationand Support Guide
Gigabit Ethernet4–Port Adapter
OSM ServiceConnection orSCF
SYSnn subvolumeC0612R00G4SAG4SA Bootfirmware
Installation andSupport Guide
Managing ServerNet Adapter Firmware 27
Managing SWAN and SWAN 2 Concentrator FirmwareBoth 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 ConcentratorInstallation and Support Guide or the SWAN 2 Concentrator Installation and Support Guide.
NOTE: Firmware levels for each component are located in the NonStop Firmware Matricesdocument.
Managing NonStop Cluster Switch FirmwareTo monitor and manage a ServerNet Cluster product configured with 6780 switches, use eitherthe OSM Service Connection or SCF commands. See the ServerNet Cluster 6780 OperationsGuide for more information.For information on required software, installation, migration, and fallback procedures, see theServerNet Cluster 6780 Planning and Installation Guide.
NOTE: Check with Scout for the latest SPRs. For firmware levels, see the NonStop FirmwareMatrices located in the Service Information section of the Support and Service collection of theNonStop Technical Library at www.hp.com/go/nonstop-docs.
Table 7 Updateable Firmware for the NonStop ServerNet Switch File Names and Locations
ToolDefault LocationFile NameComponentFirmware Name
ServerNet Cluster6780 OperationsGuide
SCF or OSMServiceConnection
SYSnn subvolumeM27896780 ClusterSwitch logic board
Router-2 ASIC*firmware
ServerNet Cluster6770 Hardware
SCF or OSMServiceConnection
SYSnn subvolumeM67706770 ClusterSwitch
Switchconfigurationfirmware Installation and
Support Guide
Managing CLIM FirmwareIf your system has CLIMs attached, it is very important that your CLIM firmware is compatible withyour system. Refer to the NonStop Firmware Matrices, located in the Service Information sectionof the Support and Service collection of the NonStop Technical Library at www.hp.com/go/nonstop-docs, and ensure you have compatible firmware levels for all CLIM components.In the past, the OSM Service Connection was used to perform the upgrade. The Down SystemCLIM Firmware Update Tool now provides a faster, more efficient method for updating CLIMfirmware in a single action while the system is halted during an RVU upgrade. To use this method,you must have:• OSM Service Connection version T0682 H02 ACV or later.
• OSM Console Tools product T0634 G06 ABB or later. When installed on the NonStop systemconsole (as part of OSM Console Tools), the Down System CLIM Firmware Update Tool islaunched from the Windows Start menu by selecting All Programs > HP OSM > Down SystemCLIM Firmware Update Tool. For information on installing OSM Console Tools, see the NonStopSystem Console Installer Guide.
To perform the CLIM Firmware upgrade when the system is halted, before halting the system, usethe OSM Service Connection and perform the Prepare for Down System CLIM Firmware Updateaction, then use the Down System CLIM Firmware Update Tool. For more information, see theCluster I/O Protocols (CIP) Configuration and Management Manual.
28 Managing Microcode and Firmware
Managing S-Series Interoperability FirmwareNOTE: See the NonStop Firmware Matrices for product levels. To find out if your NonStop systemsupports interoperability with S-series systems, see the planning guide for your system.
Table 8 Updateable Firmware for S-series Interoperability.
ToolDefault LocationFile NameFirmware NameComponent
DSM/SCM and SCFSYSnn subvolumeC0309P00SS7 Controllerfirmware, required for
CCSA
connectivity withS-series systems
OSM ServiceConnection and OSMLow-Level Link
SYSnn subvolumeSPCODE9Service Processorfirmware, required toattach an S-seriesenclosure
PMF and PMF2; IOMFand IOMF2
Managing S-Series Interoperability Firmware 29
3 Installation, Migration, and Fallback Considerations forThis RVU
See the Readme file and the appropriate softdocs for the latest information on any migration orconfiguration steps. Considerations in this chapter are categorized according to the RVU at whichthey were introduced.
J06.04
Compiling C++ Programs to Run on RVUs Earlier Than J06.04Objects compiled by the J06.04 and later C++ compilers might require new functions that are inthe current C++ Common Runtime Library but not in RVUs earlier than J06.04. Specifically, programsthat use either of the following features will fail to load because of unresolved externals (assumingthat they are not linked using the –rld_unresolved ignore option):• A try catch block
• An exception specifierTo ensure that these programs run correctly on RVUs earlier than J06.04, you must specify the-WRVU=H06.nn parameter on the c89 command (OSS or PC environment), or the RVU=H06.nnparameter on the CPPCOMP command (Guardian environment), where nn indicates the RVU onwhich the objects will run.
NOTE: The RVU and -WRVU command line parameters do not support J-series RVUs. If J06.03is the intended target system, specify H06.14.
NOTE: If you are compiling for an H-series target system, nn must be between 08 and 14,inclusive, as the Runtime Library supports only RVUs H06.08 and later.
You can fix the problem by installing T2831H01^AAD (Common Runtime Library) or later on alltarget systems that will run programs generated by the J06.04 or later version of the C++ compiler.
NOTE: You must reboot the system after installing T2831H01^AAD.
SQL/MX Versioning Feature RemovedCertain SQL/MX versioning enhancements that were introduced in an earlier H-series RVU havebeen removed in the J06.04 and later RVUs. The following enhancements are no longer supported:
• Ability of Expand-connected nodes with compatible SQL/MX versions to interoperate.
• Predictable failure on access to or from nodes with incompatible SQL/MX versions.
• Ability of each version of SQL/MX to determine compatibility.
CLIMThe CLIM is introduced in the J06.04 RVU. CLIM is a rack-mounted HP ProLiant class server thatprovides connectivity between the NonStop host system and either the network or the storagedevices. For CLIM upgrade procedures, see the Cluster I/O Protocols (CIP) Configuration andManagement Manual. For fallback procedures, see Chapter 13.CLIMs with software associated with J06.04 are not compatible with RVUs of J06.06 and laterRVUs. However, if you are migrating from a J06.04 RVU to a J06.06 or later RVU, the softwareupgrade procedures in this manual are ordered so that the CLIM and RVU compatibility is assuredbecause the RVU on the host is updated first, then, while the processors are halted, the CLIMs areupdated to the CLIM software version associated with this RVU. When the system is loaded, theCLIM and the NonStop host are at the same level and are therefore compatible.
30 Installation, Migration, and Fallback Considerations for This RVU
If the CLIM is in the STARTED state, you can determine the CLIM software version by using OSMLow 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 catsubcommand 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 SPRsthat are compatible with the host RVU. See the NonStop CLuster I/O Module (CLIM) SoftwareCompatibility Reference for all CLIM and host RVU compatibility information.See the Cluster I/O Protocols (CIP) Configuration and Management Manual for troubleshootingtips about identifying an incompatibility in CLIM and host CIP software.
J06.05
AF_UNIX Release 2 Migration and Fallback
Migrating to AF_UNIX Release 2AF_UNIX Release 2 software completely replaces earlier versions of AF_UNIX Release 1 software.There is no application migration required for AF_UNIX Release 2. The AF_UNIX Release 1semantics remain available along with the AF_UNIX Release 2 semantics. AF_UNIX Release 1semantics are the default semantics. You can choose which semantics to use either programmaticallyor by setting the Guardian DEFINE =_AFUNIX_PROCESS_NAME.AF_UNIX Release 2 software replaces the $ZPLS process pair with a per-processor process, $ZLSnn,where nn is the processor number.When migrating to AF_UNIX Release 2 (J06.05 and later RVUs):
• If you start $ZPLS in a startup script using the SCF START SERVER command, and failure tostart $ZPLS causes the script to be aborted and steps following the failing one to be omitted,modify the script to remove the command to start $ZPLS.
NOTE: In AF_UNIX Release 2, any changes to the #ZPLS attributes will have no effect.
• If you use the STARTOSS utility to start OSS processes, modify thetarget-volume.ZOSSINS.OSSINFIL file by changing the lineSERVER #ZPLS
to* SERVER #ZPLS
NOTE: target-volume is normally $SYSTEM.
NOTE: #ZPLS cannot be deleted from ZOSSSERV but can be deleted from OSSINFIL.
Commenting out the #ZPLS statement from the OSSINFIL prevents the STARTOSS utility fromissuing an error during execution.
The $ZLSnn processes are started automatically when the processors start; do not add them to anystartup or shutdown scripts.
J06.05 31
Falling Back to An Earlier Version of AF_UNIXIf fallback is required:
• If you start $ZPLS in a startup script using the SCF START SERVER command, modify startupscripts to start $ZPLS using the SCF START SERVER command.
• If you use the STARTOSS utility to start OSS processes, modify thetarget-volume.ZOSSINS.OSSINFIL file by changing the line* SERVER #ZPLS
toSERVER #ZPLS
NOTE: target-volume is normally $SYSTEM.
This ensures that the OSS Socket Local Server is started correctly as system load.
The OSS Monitor included in AF_UNIX Release 2 software adds database records for the localserver 2 (LS2) processes. If fallback is required, HP recommends that, after the system is no longerrunning an RVU containing AF_UNIX Release 2, you delete these records using the SCF DELETESERVER command:ASSUME $ZPMON DELETE SERVER#ZLS00 DELETE SERVER #ZLS01...DELETE SERVER #ZLS15
If you fail to delete the database records:• The SCF INFO SERVER command will show $ZLS00 through $ZLS15 as UNKNOWN servers
with no parameters.• Attempts to START, STOP, or ALTER $ZLS00 through $ZLS15 will fail with the diagnostic
"Configuration contains invalid data".For more information about AF_UNIX Release 2, see the Open System Services Programmer'sGuide.
CLuster I/O Module (CLIM) Software CompatibilityCLIMs with software associated with J06.05 are not compatible with RVUs of J06.06 and laterRVUs. However, if you are migrating from a J06.05 RVU to a J06.06 or later RVU, the softwareupgrade procedures in this manual are ordered so that the CLIM and RVU compatibility is assuredbecause the RVU on the host is updated first, then, while the processors are halted, the CLIMs areupdated to the CLIM software version associated with this RVU. When the system is loaded, theCLIM and the NonStop host are at the same level and are therefore compatible.If the CLIM is in the STARTED state, you can determine the CLIM software version by using OSMLow 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 catsubcommand 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 SPRsthat are compatible with the host RVU. See the NonStop CLuster I/O Module (CLIM) CompatibilityReference for all CLIM and host RVU compatibility information.See the Cluster I/O Protocols (CIP) Configuration and Management Manual for troubleshootingtips about identifying an incompatibility in CLIM and host CIP software.
32 Installation, Migration, and Fallback Considerations for This RVU
J06.06
CLuster I/O Module (CLIM) Software CompatibilityFor J06.06 and subsequent J-series RVUs, CLIM software associated with the RVU is compatiblewith 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 atthe 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 areupgrading.
If you are migrating from a J06.06 or later RVU, you can perform an online upgrade to the CLIMsbefore upgrading the host system.If the CLIM is in the STARTED state, you can determine the CLIM software version by using OSMLow 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 catsubcommand 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 SPRsthat are compatible with the host RVU. See the NonStop CLuster I/O Module (CLIM) CompatibilityReference for all CLIM and host RVU compatibility information.See the Cluster I/O Protocols (CIP) Configuration and Management Manual for troubleshootingtips about identifying an incompatibility in CLIM and host CIP software.
DSM/SCM Upgrade Issues/Interoperability SPR RequirementsIf you are migrating from an J06.05 or earlier RVU to a J06.06 or later RVU, be aware that allthe DSM/SCM target systems should be upgraded before the DSM/SCM host is upgraded. Thesnapshot file created by T6031 H02 ACL has changed and cannot be read by earlier versions ofDSM/SCM. See Support Note S09036 for more information.
J06.07
Falling Back to iLO Firmware T0848AAAAfter updating the iLO firmware to T0848AAB or later (iLO version 1.77 or later), subsequentattempts to downgrade to T0848AAA (iLO version 1.50) using OSM Service Connection willgenerate an action failure message indicating that the downgrade operation has failed:iLo Firmware update failed. Please perform the following steps. 1. Retry the operation. 2. If the operation fails again, reset the iLo and then retry the operation again. 3. If the operation fails a third time, contact your service provider.
Additional information (may be useful to service provider): Firmware Update on Clim: C100251, failed with the following error:comForte SSH client version T9999H06_20Mar2009_comForte_SSH_0085 Downloading firmware (1.50) to iLo ... Failed Error: Firmware download failed. Error (1): Operation failed. STOPPED: $Z14N CPU time: 0:00:00.007 2: Process terminated with fatal errors or diagnostics
Before retrying the downgrade operation, perform a CLIM Rediscovery from the OSM ServiceConnection to determine if the iLO firmware has actually been downgraded. The iLO firmwaredowngrade operation should have succeeded in most cases even though the OSM ServiceConnection Action result indicates a failure result. If, after the CLIM Rediscovery action is completed,the reported iLO level matches the expected level, then the failure result associated with thedowngrade action can be safely ignored.
J06.06 33
DSM/SCM Upgrade Issues/Interoperability SPR RequirementsIf you are migrating from a J06.04 or earlier RVU to a J06.07 or later RVU, be aware that theUSERID attributes of all persistent processes configured under $ZZKRN might change fromSUPER.SUPER to NULL.NULL. If this occurs on a system where $SYSTEM is using FCDM diskenclosures connected by FCSAs in IOAM enclosures, the system might halt when a system load tothe new RVU is attempted. To prevent this problem, you must install DSM/SCM SPR T6031H02^ACJor later on your system. See Hotstuff HS03058 for more information.
J06.08
NonStop SQL/MXThe J06.08 RVU introduces the large block support feature (32 KB blocks) for NonStop SQL/MXtables. This feature requires a new revision of the HP NonStop Remote Database Facility (RDF,T0346). For systems running J06.08, the RDF version is compatible only with T0346H09^ACCand later SPRs of RDF. For more information, see the T0346 softdoc.For the J06.08 RVU, the versions of RDF on primary and backup systems that are supported acrossdifferent RVUs are:
Table 9 NonStop SQL/MX and Supported RDF Versions
RDF SPR on BKUPRDF SPR on PRIRVU on BKUPRVU on PRI
H09^ACCH09^ACCJ06.08J06.08
H09^ACCH09^ACCJ06.08J06.03 to J06.07
H09^ACCA07^ACAJ06.08G06.03 and later
J06.09This section describes changes to default behavior introduced by new features at J06.09. For acomplete list of new features, migration issues and fallback considerations, see the J06.09 ReleaseVersion Update Compendium.
SQL/MX 2.3.4 Requires JDBC T2 DriverJDBC T2 Driver must be installed on J06.09 and later J-series RVUs to support SQL/MX 2.3.4.
BladeCluster Solution Multi-Zone SupportMulti-zone topologies, introduced at J06.09 but supported back to J06.04, require software licencesand other components on all nodes within the zones. See the J06.09 Release Version UpdateCompendium for a high-level list of these requirements.
J06.10This section provides information only for new features and changes that affect the softwareinstallation and upgrade steps for J06.10. See the J06.10 Release Version Update Compendiumfor a complete list of new features and associated migration and fallback alerts.
NonStop SOAP 4NonStop SOAP 4 migration issues exist for NonStop SOAP 3 to NonStop SOAP 4 upgrades. Seethe J06.nn Release Version Update Compendium for this RVU for a list of migration issues andworkarounds.
34 Installation, Migration, and Fallback Considerations for This RVU
New CLuster I/O Module (CLIM) Storage DevicesHP introduces (controlled availability) support for next-generation CLIMs and storage devices. Thenew CLIMs and storage devices require J06.06 and later J-series RVUs. All software required forthese components is included with this RVU.See the planning guide for your system for information about the CLIMs and storage devices.The new devices require the J06.06 or later J-series RVU. If you must fall back to an earlier RVU,you cannot use the new CLIMs or SAS disk enclosures. If you fall back to an RVU between J06.06and J06.09 inclusive, you must add SPRs to those RVUs to support the new CLIMs and diskenclosures because falling back to a previous RVU removes the required software. For a list ofrequired SPRs for these components, see the CLuster I/O Module (CLIM) Software CompatibilityReference.The next-generation CLIMs and storage devices only work with each other. They cannot be mixedwith the previous generation CLIMs and storage devices.
Other CLIM and CIP ChangesThe Telco CLIM now supports CLIM failover.This RVU also includes new features to solve the issue of CLIMs trying to send data on down-link-pulseinterfaces and to provide more control over routing.CIP now supports audit logging for commands executed on a CLIM using CLIMCMD.See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more informationabout these features.
Hardware and NetworkingAs of J06.03, Token-Ring and System Signaling Seven (SS7) connectivity is supported on NonStopBladeSystems through the NonStop S-series I/O enclosure. For more information, see the NonStopBladeSystem Planning Guide.
New Operating System FeaturesJ06.10 adds several new operating system features, most of which have migration and fallbackissues. See the J06.10 Release Version Update Compendium for more information about thesefeatures.
TMF 3.6Fallback considerations exist for TMF 3.6 enhancements. See the J06.10 Release Version UpdateCompendium for this RVU for more information.
iTP WebServer 7.2Migration and fallback considerations exist for iTP WebServer 7.2. See the J06.10 Release VersionUpdate Compendium for this RVU for more information.
Expand Enhancements.Fallback considerations exist for the Expand enhancements. See the J06.10 Release Version UpdateCompendium for more information.
J06.11This section provides information only for new features and changes that affect the he softwareinstallation and upgrade steps for J06.11. See the J06.11 Release Version Update Compendiumfor a complete list of new features and associated migration and fallback alerts.
J06.11 35
Changes to SSOCLIM Privilege RequirementThe privilege for running SSOCLIM, which was SUPER.SUPER for J06.09 and J06.10, has beenchanged to any SUPER group user. SSOCLIM is run after a fallback. For details, see CompleteCLIM Set Up in Chapter 13: “Falling Back on the CLIMs, Loading the Previous RVU, and ResumingNormal Operations ” (page 114).
J06.12This section provides information only for new features and changes that affect the softwareinstallation and upgrade steps for J06.12. See the J06.12 Release Version Update Compendiumfor a list of new features and associated migration and fallback alerts.
HP SUMThe introduction of HP SUM affects upgrade steps for NonStop NS2200 series, NS2100, andNonStop BladeSystem NB54000c and NB54000c-cg servers. See Chapter 4: “Upgrade Checklist”(page 39) and “Perform Updates” (page 91).
J06.13This section provides information only for new features and changes that affect the softwareinstallation and upgrade steps for J06.13. See the J06.13 Release Version Update Compendiumfor a list of new features and associated migration and fallback alerts.
SafeguardFallback and migration considerations exist for the new Safeguard features. See the J06.13 ReleaseVersion Update Compendium for more information.
Considerations Exist for Fallback to J06.11Fallback considerations exist for NB54000c-cg systems falling back to J06.11. See support noteS11046.
Performance Tuning RequirementsSteps to tune performance exist on certain combinations of NonStop servers and J-series RVUs.See Support Note S11044 for more information.
Core License FileThe core licensing option on BladeSystems NB54000c and NB54000c-cg, introduced and requiredwith J06.13, affects installation steps. For more information about the core license file, refer to theNonStop BladeSystem Planning Guide.
Migrating a NonStop BladeSystem NB50000c to an NB54000c or NB50000c-cgto an NB54000c-cg
The core license file requires the CLICVAL tool, which affects preparation steps. For more information,see “Upgrade Checklist” (page 39), “Preparing to Upgrade the Server Software (PreinstallationTasks)” (page 44), and the NonStop BladeSystem Planning Guide..
Upgrading a NonStop BladeSystem NB54000c or NB54000c-cg to J06.13 or LaterRVUs
Before upgrading to the J06.13 RVU or a later RVU, you must obtain the Core License Validationtool (CLICVAL). For more information, refer to the NonStop BladeSystem Planning Guide. Prior toupgrading to J06.13 or a later RVU, you use the CLICVAL tool to verify the core license file is valid.
36 Installation, Migration, and Fallback Considerations for This RVU
After upgrading to J06.13, HP recommends that you use the OSM action, Read Core License toverify that the core license is valid. See the upgrade checklist in “Upgrade Checklist” (page 39).
HP NonStop Software EssentialsHP NonStop Software Essentials is a software installation and management tool for NonStopservers. Installed as a plug-in to HP SIM, NonStop Software Essentials uses DSM/SCM serversoftware and provides a replacement for certain DSM/SCM Planner Interface functions that ismore secure, easier to use, and overcomes other shortcomings of DSM/SCM. It coexists withDSM/SCM; you can use either NonStop Software Essentials or the DSM/SCM Planner Interfacefor tasks in which there is overlapping functionality. For more information, see the NonStop SoftwareEssentials Installation and Quick Start Guide.
IB CLIM Fallback ConsiderationsThe IB CLIM is supported as of J06.12. If you fall back to J06.12 and have IB CLIMs, after youreimage the CLIMs, you must select Open for mode and the CLIM model should show 3 copper2 IB. See “Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations” (page 114).
EXTDECSLAn SPR for T9003H01, ACC, exists in J06.13. If the application is using any of the new featuresintroduced by this SPR, the application requires recompilation. If the application is not using anyof the new features introduced by this SPR, recompilation using the SPR preceding the current SPRis enough. If the application is using any of the new features, remove the new features beforerecompiling the application with a prior SPR of EXTDECS.
TNS/E ECOBOLAn SPR for T0356H01, ABI, exists in J06.13. To fall back to a prior RVU, after fallback, recompilethe application with the ECOBOL SPR that precedes this SPR.
J06.14This section provides information only for new features and changes that affect the softwareinstallation and upgrade steps for J06.14. See the J06.14 Release Version Update Compendiumfor a list of new features and associated migration and fallback alerts.
Halt and Hard Reset Processors When Upgrading to J06.14When upgrading to J06.14 from an earlier RVU, the processors must be hard reset after they arehalted and before loading the system as described in “5. (Required for Upgrade to J06.14) Resetthe System Firmware” (page 93).
SQL/MX Release 3.2SQL/MX Release 3.2 replaces SQL/MX Release 2.3.4 as the default version on the SUT startingwith J06.14 and H06.25. Users have a choice of staying with the latest SQL/MX Release 2.3.4SPRs released as Time Critical Fixes (TCFs) or to migrate to SQL/MX Release 3.2. Please refer tothe instructions in hotstuff HS03173 for more details before installing J06.14 or H06.25.
HP Power RegulatorJ06.14 is the first RVU to support Power Regulator. For more information, see “FallbackConsiderations for the Power Regulator” (page 114).
J06.14 37
SafeguardFallback and migration considerations exist for the new Safeguard features. See the J06.14 ReleaseVersion Update Compendium for more information.
38 Installation, Migration, and Fallback Considerations for This RVU
4 Upgrade ChecklistUse the upgrade checklist in “Upgrade Checklist” (page 40) to track your progress as you performthe tasks required to upgrade to this RVU and the checklists in Table 10 and Table 11 (page 40)to record the information needed when performing these tasks.
CAUTION: The upgrade steps must be performed in the order specified in this chapter.
NOTE: To perform these upgrade tasks, you need the NonStop System Console (NSC) InstallerGuide. If your system has CLIMs, you also need the Cluster I/O Protocols (CIP) Configuration andManagement Manual the CLuster I/O Module (CLIM) Software Compatibility Reference, NonStopFirmware Matrices.
NOTE: If you are migrating from a J06.06 or later RVU, you can perform an online upgrade ofthe CLIMs before upgrading the host system. (See the Cluster I/O Protocols (CIP) Configurationand Management Manual for online CLIM software upgrade procedures.) If you have not alreadyupgraded your CLIMs, you will need to upgrade the CLIMs offline as shown in this procedure.
You might have to update the service processor (SP) firmware on NonStop S-series systems forIOMF2 PMF CRUs.
Required Information ChecklistsGather the information in Table 10 before you start. Obtain firmware levels from the CLuster I/OModule (CLIM) Software Compatibility Reference.
Table 10 Required Information Checklist, Before You Start
ValueType of Information
Volume where SYSnn subvolumes are located (usually $SYSTEM)
Current SYSnn (before upgrading to this RVU)
FCSA firmware
G4SA firmware
c7000 enclosure ServerNet Switch firmware
OA firmware level
• ServerNet Switch firmware
• ServerNet Switch FPGA firmware
CLIM software
CLIM firmware
S-Series Interoperability firmware
• Service Processor
• Service Processor B
IOAM or VIO firmware
• ME firmware
• ME FPGA firmware
SWAN firmware
Required Information Checklists 39
Table 10 Required Information Checklist, Before You Start (continued)
ValueType of Information
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 11 Information to Gather During the Upgrade (Checklist)
ValueType of Information
SYSnn created during this RVU Build/Apply
Volume where ZDSMSCM subvolume is located (by default,$DSMSCM)
Volume where audit trails are located (by default, $AUDIT)
Name of saved configuration file
Upgrade ChecklistGo through this list in order and check off each task in the Done column after it is complete.
Table 12 Upgrade Checklist
Done?ReferenceTask Description
“Preparing to Upgrade the Server Software (PreinstallationTasks)” (page 44)
1. Perform all the necessarypre-installation tasks before updatingthe system console and receiving theSUT.
Appendix C: “Installing SWID and DSM/SCM PVU UsingNonStop Software Essentials Client Software ” or “Using
2. Install DSM/SCM client andserver, if necessary. Update
DSM/SCM and Planner Interface to Install SPRs”(page 146)
DSM/SCM EMS template files, ifnecessary.
“Back Up Important Files” (page 44)3. Back up important files.
“Record the Current SYSnn” (page 45) and Table 10(page 39)
4. Record the current SYSnn.
“Save the Current Configuration File (CONFxxyy)”(page 45)
5. Save current system configurationfile.
6. Install required or recommendedfallback SPRs and nodeinteroperability SPRs, if necessary.
• Appendix A: “Using DSM/SCM and NonStopSoftware Essentials to Install SPRs” or “UsingDSM/SCM and Planner Interface to Install SPRs”(page 146) (procedures)
• “Install Node Interoperability SPRs” (page 52) (list ofrequired SPRs)
“Updating System Consoles (Optional)” (page 15)7. Upgrade system console software.
40 Upgrade Checklist
Table 12 Upgrade Checklist (continued)
Done?ReferenceTask Description
1. Prior to upgrading to J06.13, use the CLICVAL tool toverify the core license file is valid. For more information
8. (Optional) For NonStopBladeSystems
on using CLICVAL, refer to the TACL Reference Manualand NonStop BladeSystem Planning Guide.
NB54000c/NB54000c-cg, if youare migrating to J06.13, use the
Note: If CLICVAL cannot verify your core license file, youmust order a new one as described in the NonStopBladeSystem Planning Guide.
CLICVAL tool to verify your licensefile.
2. After upgrading to J06.13, HP recommends that youuse the OSM Read Core License action to verify that thecore license is valid. Later in this checklist, you will bereminded to perform this action.IMPORTANT: If your license file is invalid or missing, youmust correct this problem. For more information, refer tothe NonStop BladeSystem Planning Guide.
9. Install and configure the latestHalted State Services firmware, if
• NonStop System Console (NSC) Installer Guide(procedures)
necessary (includes DISKBOOT and• NonStop Firmware Matrices (firmware levels reference)ISP1040 firmware). Note: This step
is not applicable to NonStopNS2000 series systems.
“Verify System Processes” (page 46)10. Verify system operations.
Cluster I/O Protocols (CIP) Configuration andManagement Manual (installation procedures), CLuster
11. Install CLIM software on NonStopSystem Console.
I/O Module (CLIM) Software Compatibility Reference(CLIM software and firmware compatibility information)
“Receive New Software Into the Archive” (page 55)12. For those with NonStop SoftwareEssentials, receive this RVU SUT intothe DSM/SCM software archive.
“Receive New Software Into the Archive” (page 68)13 For those with the DSM/SCMPlanner Interface, receive this RVUSUT into the DSM/SCM archive.
“Create a New Software Revision” (page 58)14. For those with NonStop SoftwareEssentials, create this RVU softwareconfiguration revision.
“Create a New Software Revision” (page 72)15. For those with the DSM/SCMPlanner Interface, create this RVUsoftware configuration revision.
“Build and Apply the New Software Revision” (page 61)16. For those with NonStop SoftwareEssentials, build and apply this RVUsoftware revision.
“Build and Apply the New Software Revision” (page 75)17. For those with the DSM/SCMPlanner Interface, build and applythis RVU software revision.
“Print Operator Instructions From the Target Interface(ZPHITI)” (page 64)
18. Print DSM/SCM OperatorInstructions.
Chapter 8: “Running ZPHIRNM ”19. Run ZPHIRNM.
“2. Halt the Processors” (page 92)20. Halt processors.
“3. (Optional): Update System Firmware Using HP SUM”(page 92)
21. (Optional) Update systemfirmware using HP SUM (applicableto NonStop NS2200 series,NS2100, and NonStop BladeSystem
Upgrade Checklist 41
Table 12 Upgrade Checklist (continued)
Done?ReferenceTask Description
NB54000c servers only and notalways required)
“4. (Optional): Update HSS Firmware ” (page 92)22. If Halted State Services firmwareis being upgraded, hard reset theprocessors. Note: This step is notapplicable to NonStop NS2000series systems. Also, if upgrading aNonStop NS2200 series, NS2100,or NonStop BladeSystem NB54000cserver, if you performed step 16(updating system firmware using HPSUM), a power cycle has occurredand hard resetting the processorsagain is not necessary.
This update is done through a Field Change Order (FCO).23. Update C7000 Enclosurefirmware, if necessary.
Cluster I/O Protocols (CIP) Configuration andManagement Manual
24. Update CLIM software on allCLIMs using the procedurePerforming the CLIM SoftwareUpgrade Using OSM Low-Level Link.(If you are migrating from J06.06 orlater and performed an onlineupgrade of the CLIM to the CLIMsoftware released with this RVUbefore starting the host systemupgrade, you can skip this step.)
“7. Loading the System” (page 93)25. Load the system with new thisRVU.
Use the OSM Read Core License action to verify that thecore license is valid.
26. For NonStop BladeSystemNB54000c and NB54000c-cg,verify the system's core license file. IMPORTANT: If your license file is invalid or missing, you
must correct this problem. For more information, refer tothe NonStop BladeSystem Planning Guide.
“Managing S-Series Interoperability Firmware” (page 29)27. Update S-series interoperabilityfirmware, if necessary.
“Updating ME Firmware” (page 22)28. Update ME and ME FPGAfirmware, if necessary.
“Managing ME Firmware and ME FPGA Firmware”(page 22) and the CSSI web page
29. For systems with IOAMs, updateIOAM firmware, if necessary.
“Managing ServerNet Adapter Firmware” (page 25)30. Update FCSA firmware, ifnecessary.
“Managing ServerNet Adapter Firmware” (page 25)31. Update G4SA Boot firmware, ifnecessary.
This update is done through a Field Change Order (FCO).32. Update remaining server bladefirmware, if necessary.
“Managing ServerNet Adapter Firmware” (page 25)33. Update G4SA Download Codefirmware, if necessary.
“Managing CLIM Firmware” (page 28)34. Update firmware for CLIMcomponents, if necessary.
“Update NonStop TCP/IP Configuration Files” (page 100)35. Recover TCP/IP files, ifnecessary.
42 Upgrade Checklist
Table 12 Upgrade Checklist (continued)
Done?ReferenceTask Description
“Check Processor Status ” (page 46)36. Check processor status.
“Configure the WAN Manager” (page 103)37. Configure WANMGR, ifnecessary.
SWAN Concentrator Installation and Support Guide orSWAN 2 Concentrator Installation and Support Guide
38. Update SWAN concentrator CLIPfirmware, if necessary.
“Start System Applications” (page 98)39. Start system software.
“Configure OSS” (page 102)40. Configure OSS, if necessary.
“Configure SMF (Optional)” (page 103)41. Configure SMF, if necessary.
“Configure the Remote Database Facility” (page 103)42. Configure RDF, if necessary.
“Set Up iTP Webserver” (page 104)43. Set up iTP WebServer, if installedon the previous RVU.
“Re-deploy NonStop SOAP 4” (page 104)44. Re-deploy NonStop SOAP 4, ifinstalled on the previous RVU.
You application documentation45. Start applications.
Upgrade Checklist 43
5 Preparing to Upgrade the Server Software (PreinstallationTasks)
Before updating the system console and receiving the SUT, perform these tasks:
Back Up Important FilesBefore you upgrade, create tape backups of critical host applications and files.
Back Up NonStop SQL/MPHP recommends that you always have a current backup copy of the $SYSTEM.SYSTEM.ZZSQLCI2file in case you need to initialize SQL later if you have problems with your new RVU during orafter installation.1. Save a copy of the existing ZZSQLCI2 file on the $SYSTEM disk. For example:
> FUP DUP $SYSTEM.SYSTEM.ZZSQLCI2,$SYSTEM.BKUPZSQL.*, SAVEALL
2. Enter:
> SQLCI INITIALIZE SQL; EXIT;
3. Copy the ZZSQLCI2 file saved previously back to the $SYSTEM disk. For example:
> FUP DUP $SYSTEM.BKUPZSQL.ZZSQLCI2, $SYSTEM.SYSTEM.*, SAVEALL
Back Up NonStop SQL/MX filesSee the NonStop SQL/MX Release 3.2 Installation and Upgrade Guide.
Back Up Spooler Control filesBefore executing the SPOOLCOM;SPOOLER,DRAIN command:
• Use the SPOOLCOM;COLLECT $collector-process, LISTOPENS command to identifyprocesses that currently have jobs open.
• Use the SPOOLCOM;JOB (STATE PRINT) command to determine which jobs are currentlyprinting.
Take the appropriate action to ensure that these jobs either terminate when finished or are stopped.
CAUTION: To maintain the integrity of the spooler environment, wait until the spooler has finisheddraining rather than stop any spooler processes by using the TACL STOP command. The controlfile can be corrupted during the next warm start or rebuild.
An example of backing up the spooler control files:
BACKUP/OUT SPLBKUP/$TAPE,($SYSTEM.SPOOLER.*,$DATA01.SPOOLER.DATA),LISTALL
Back Up TMF FilesUse the OBEYFORM option available in TMFCOM INFO commands to save current configurationinformation in command files.
Back Up CLIM Configuration FilesBack up CLIM configuration files for each CLIM using the TACL command CLIMBKUP.
44 Preparing to Upgrade the Server Software (Preinstallation Tasks)
NOTE: If you must fall back to this RVU, you need to restore these saved configuration filesbecause 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 renameeach backup file after you create it. The default file name for the backup is backupgz. Renamethese as you create them. For example:1. CLIMBKUP N1002583 $DATA1.BCKJ06052. FUP RENAME $DATA1.BCKJ0605.BACKUPGZ, $DATA1.BCKJ0605.N10025833. CLIMBKUP N1002582 $DATA1.BCKJ06054. FUP RENAME $DATA1.BCKJ0605.BACKUPGZ, $DATA1.BCKJ0605.N1002582For upgrades from J06.06, you can specify a unique filename in the same command. For example,>CLIMBKUP N1002583 $system.N1002583.BCKJ0606
Record the Current SYSnnIdentify and record the current SYSnn subvolume on your system. You will have to specify thisSYSnn subvolume if you need to fall back from this RVU.At a TACL prompt, issue the status command to determine the current SYSnn subvolume. Forexample:3> status 0,0
System \ELIProcess Pri PFR %WT Userid Program file Hometerm 0,0 201 P R 000 255,255 $SYSTEM.SYS01.OSIMAGE $YMIOP.#CLCI Swap File Name: $SYSTEM.#0
Save the Current Configuration File (CONFxxyy)A saved system configuration file contains a copy of the current configuration database CONFIGfile, saved for future use. For fallback purposes, save a copy of the current CONFIG file by usinga unique file name. Do not omit this step.You can use the saved configuration file to return to an earlier, stable configuration. If you needto fall back to the previous RVU, you must load the system by using a saved configuration file andthe SYSnn containing the previous operating system.To save the current system configuration database CONFIG file, use the SCF SAVE command:1. At a TACL prompt, start SCF:
12> SCF
2. List the saved configuration files. At the SCF prompt, enter:-> FUP INFO $SYSTEM.ZSYSCONF.CONF*
3. Save the current configuration by using a unique file name. At the prompt, enter:-> SAVE CONFIGURATION xx.yy
where xx.yy is a number from 0.0 through 99.99.
This example saves the current system configuration to the file $SYSTEM.ZSYSCONF.CONF1101:-> SAVE CONFIGURATION 11.1The configuration file $SYSTEM.ZSYSCONF.CONF1101 has been created.
Record the Current SYSnn 45
Verify System Processes
Check Processor Status1. 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 beExecuting NonStop OS.
Check System Components1. 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.
46 Preparing to Upgrade the Server Software (Preinstallation Tasks)
The system name box in the Physical view indicates the overall health of a system by the colorof the system icon. Green indicates no problems reported by OSM. Yellow indicates a possiblesystem problem.
2. Double-click to expand the object further to identify components that require attention (yellowor a yellow arrow) or immediate service (red).
CAUTION: If a red triangle appears over an object, or if any component is highlighted inred, contact your HP Service Provider.
3. For each Enclosure object, double-click the Enclosure object (Enclosure 100 and, optionally,Enclosure 101).
4. For each Logical Processor in the Enclosure object:a. Select the Logical Processor.b. In the Attributes tab, verify the values of the following attributes:
• Halt Flag should have a value of False
• Processor State (from ME) should have a value of Running NSK
• Logical Processor State should have a value of Up
NOTE: If the Halt Code or Halt Flag attributes do not match these values, see theProcessor Halt Codes Manual.
Verify System Processes 47
Verify the State of the Internal ServerNet FabricTo 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 FirmwareUse the OSM Service Connection to verify that all updateable firmware is at the proper revisionlevel for your current RVU. For more information on updating firmware, see “Managing ServerBlade Firmware” (page 24) and the OSM Service Connection User’s Guide.
48 Preparing to Upgrade the Server Software (Preinstallation Tasks)
Verify Critical System Processes1. From a TACL prompt, log on to the system using the super ID (255,255). Enter the LISTDEV
command:> SCF LISTDEV$ADBIT RESULTS 18> scfSCF - 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.SCFCSTM)1-> listdev
LDev Name PPID BPID Type RSize Pri Program 0 $0 0,3 1,3 ( 1,0 ) 102 201 \ATLAS.$SYSTEM.SYS15.OPCOLL 1 $NCP 0,14 1,14 (62,6 ) 3 199 \ATLAS.$SYSTEM.SYS15.NCPOBJ 3 $YMIOP 0,5 1,5 ( 6,4 ) 80 205 \ATLAS.$SYSTEM.SYS15.TMIOP 5 $Z0 0,7 1,7 ( 1,2 ) 102 200 \ATLAS.$SYSTEM.SYS15.OCDIST 6 $SYSTEM 0,257 1,257 ( 3,53) 4096 220 \ATLAS.$SYSTEM.SYS15.TSYSDP2 7 $ZOPR 0,8 1,8 ( 1,0 ) 102 201 \ATLAS.$SYSTEM.SYS15.OAUX 63 $ZZKRN 0,295 1,363 (66,0 ) 4096 180 \ATLAS.$SYSTEM.SYS15.OZKRN 64 $ZZWAN 0,292 1,342 (50,3 ) 132 180 \ATLAS.$SYSTEM.SYS15.WANMGR 65 $ZZW03 3,284 0,0 (50,0 ) 0 199 \ATLAS.$SYSTEM.SYS15.CONMGR 66 $ZZW02 2,284 0,0 (50,0 ) 0 199 \ATLAS.$SYSTEM.SYS15.CONMGR 67 $ZZW01 1,285 0,0 (50,0 ) 0 199 \ATLAS.$SYSTEM.SYS15.CONMGR 68 $ZZW00 0,324 0,0 (50,0 ) 0 199 \ATLAS.$SYSTEM.SYS15.CONMGR 69 $ZZTCP 0,337 1,323 (72,0 ) 132 200 \ATLAS.$SYSTEM.SYS15.TCP6MAN 70 $ZZSTO 0,293 1,364 (65,0 ) 4096 180 \ATLAS.$SYSTEM.SYS15.TZSTO 71 $ZZSMN 0,338 1,339 (64,1 ) 132 180 \ATLAS.$SYSTEM.SYS15.SANMAN 72 $ZZSCL 0,336 1,335 (64,0 ) 132 199 \ATLAS.$SYSTEM.SYS15.SNETMON 73 $ZZLAN 0,294 1,341 (43,0 ) 132 199 \ATLAS.$SYSTEM.SYS15.LANMAN 74 $ZWBAB 0,323 1,343 (50,4 ) 132 179 \ATLAS.$SYSTEM.SYS15.WANBOOT 75 $ZWBAA 0,322 1,344 (50,4 ) 132 179 \ATLAS.$SYSTEM.SYS15.WANBOOT 85 $ZSNET 0,295 1,363 (66,0 ) 4096 180 \ATLAS.$SYSTEM.SYS15.OZKRN 86 $ZSLM2 0,290 1,321 (67,0 ) 1024 221 \ATLAS.$SYSTEM.SYS15.TZSLM2 89 $ZNET 0,155 1,176 (50,63) 3900 175 \ATLAS.$SYSTEM.SYS15.SCP 90 $ZM03 3,281 0,0 (45,0 ) 132 201 \ATLAS.$SYSTEM.SYS15.QIOMON 91 $ZM02 2,281 0,0 (45,0 ) 132 201 \ATLAS.$SYSTEM.SYS15.QIOMON 92 $ZM01 1,282 0,0 (45,0 ) 132 201 \ATLAS.$SYSTEM.SYS15.QIOMON 93 $ZM00 0,296 0,0 (45,0 ) 132 201 \ATLAS.$SYSTEM.SYS15.QIOMON 94 $ZLOG 0,339 1,375 ( 1,0 ) 4024 150 \ATLAS.$SYSTEM.SYS15.EMSACOLL
Verify Disk Drives1. Enter the SCF STATUS DISK command:
> SCF STATUS DISK $*
2. Verify that the STATUS DISK display includes all the disk drives and that the primary, backup,mirror, and mirror-backup paths are all described as STARTED:
$SYSTEM TOOLS 48> SCF STATUS DISK $*
SCF - T9082H01 - (01MAY08) (15MAR08) - 07/06/2008 10:55:16 System \ATLAS(C) 1986 Tandem (C) 2003 Hewlett Packard Development Company, L.P.STORAGE - Status DISK \ATLAS.$SYSTEM
LDev Primary Backup Mirror MirrorBackup Primary Backup PID PID 6 *STARTED STARTED STOPPED STOPPED 0,257 1,257
STORAGE - Status DISK \ATLAS.$AD01 LDev Primary Backup Mirror MirrorBackup Primary Backup PID PID 152 *STARTED STARTED STOPPED STOPPED 0,333 1,288
STORAGE - Status DISK \ATLAS.$ADAUD LDev Primary Backup Mirror MirrorBackup Primary Backup PID PID
Verify System Processes 49
151 *STARTED STARTED *STARTED STARTED 0,332 1,289
STORAGE - Status DISK \ATLAS.$ADBIT LDev Primary Backup Mirror MirrorBackup Primary Backup PID PID 150 *STARTED STARTED *STARTED STARTED 0,331 1,290
STORAGE - Status DISK \ATLAS.$ADSAV LDev Primary Backup Mirror MirrorBackup Primary Backup PID PID 149 *STARTED STARTED STOPPED STOPPED 0,330 1,291
Total Errors = 0 Total Warnings = 0$SYSTEM TOOLS 49>
Verify Tape Drives (If Necessary)You can use SCF commands or OSM to obtain status information about a tape drive. Check thatthe tape drive is online before continuing with installing SPRs, RVUs, or RVURs. OSM does not testtape libraries.1. Enter the SCF STATUS TAPE command:
> SCF STATUS TAPE $*
2. Verify that the STATUS TAPE display includes a least one tape drive configured and running,as shown:
STORAGE - Status TAPE $T0150
LDev State Sub State Primary Backup Device Status PID PID 71 STARTED UP 0,282 1,273 READY
3. Use the SCF STATUS TAPE, DETAIL command to display the current state of the tape drive.4. If the status of the tape drive is stopped or not ready, start the tape drive and put the tape
drive online.
Verify That the CLIMs Are in the Started State1. Enter the SCF STATUS CLIM command:
-> STATUS CLIM $ZZCIP.*
2. Verify that the state of all configured CLIMs is STARTED:CIP Status CLIM \MYSYS.$ZZCIP.*
Name Present State TraceN1002532 Yes STARTED OFFN1003741 Yes STARTED 1, 2N1012542 Yes STARTED 2
Verify That the CIP Providers Are in the Started State1. Enter the SCF STATUS PROV command:
-> STATUS PROV $ZZCIP.*
2. Verify that the status of all providers is STARTED:CIP Status PROVIDER
Name Status TPStatus Trace
50 Preparing to Upgrade the Server Software (Preinstallation Tasks)
ZCSAM STARTED Started OFFPROV1 STARTED Invalid (0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15)
Check the Status of the Spooler CollectorCheck 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 STATE FLAGS CPU PRI UNIT DATA FILE %FULL$S ACTIVE 3 , 1 154 4 $OPS0.SPL.DATA 44
Check for Sufficient Swap File SpaceYou must ensure that you have configured kernel-managed swap files of sufficient size for all yoursystem and application software processes. The optimal amount of swap space varies, dependingon the configuration of your system. You must be a super-group user (255, n) in order to changethe KMSF configuration by adding, altering, stopping, or deleting swap space. Only one super-groupuser at a time can use NSKCOM to change the configuration.KMSF swap files need to be larger than in G-series RVUs. The best practice is to monitor swap fileusage. See the Kernel-Managed Swap Facility (KMSF) Manual for information on configuring swapfile space.To check the size of the configured swap files for each processor:1. At a TACL prompt, start NSKCOM:
$SYSTEM STARTUP 5> nskcomNSKCOM - T5838H01 BASE (01OCT07) - Apr 15 2008Copyright 1995 Compaq Computer Corporation
$SYSTEM.SYSTEM.ZSYSCFGKMS.SWAPFILE = 0 $SYSTEM.ZSYSSWAP.SWAP00KMS.SWAPFILE = 1 $SYSTEM.ZSYSSWAP.SWAP01KMS.SWAPFILE = 2 $SYSTEM.ZSYSSWAP.SWAP02KMS.SWAPFILE = 3 $SYSTEM.ZSYSSWAP.SWAP03
2. Issue the STATUS SWAPFILE * command to display the peak pages reserved so that youcan compare that information to the total amount of swap space available.
$SYSTEM TOOLS 50> nskcom STATUS SWAPFILE *NSKCOM - T5838H01 BASE (01OCT07) - Jun 17 2008Copyright 1995 Compaq Computer Corporation
$SYSTEM.SYSTEM.ZSYSCFGKMS.SWAPFILE = 0 $SYSTEM.ZSYSSWAP.SWAP00KMS.SWAPFILE = 1 $SYSTEM.ZSYSSWAP.SWAP01KMS.SWAPFILE = 2 $SYSTEM.ZSYSSWAP.SWAP02KMS.SWAPFILE = 3 $SYSTEM.ZSYSSWAP.SWAP03
Status of $SYSTEM.ZSYSSWAP.SWAP00CPU 0CPU Pages: Total 102305* Reserved 14936 Available 87369Peak CPU Pages ever reserved 101855Threshold 86959 CPU pages* Default swapfile extents may not be fully allocated.
Status of $SYSTEM.ZSYSSWAP.SWAP01CPU 1CPU Pages: Total 102305* Reserved 12213 Available 90092Peak CPU Pages ever reserved 15239
Verify System Processes 51
Threshold 86959 CPU pages* Default swapfile extents may not be fully allocated.
Status of $SYSTEM.ZSYSSWAP.SWAP02
CPU 2CPU Pages: Total 102305* Reserved 6361 Available 95944Peak CPU Pages ever reserved 7280Threshold 86959 CPU pages* Default swapfile extents may not be fully allocated.
Status of $SYSTEM.ZSYSSWAP.SWAP03CPU 3CPU Pages: Total 102305* Reserved 5242 Available 97063Peak CPU Pages ever reserved 6863Threshold 86959 CPU pages* Default swapfile extents may not be fully allocated..
Install Node Interoperability SPRsNode interoperability is the ability of the nodes (systems) in an Expand network to communicateand interact with each other. An Expand network can be interconnected using various technologiessuch as Expand over IP and ServerNet Cluster. See the NonStop Networking Overview for moreinformation about and diagrams of NonStop platform interoperability.In addition to interoperability issues for nodes connected through Expand, there are softwaremigration and software management issues to consider, such as accelerating TNS object files ona system running an RVU series for posterior use in a system running another RVU series, DSM/SCMsoftware management in an environment composed of systems running different RVU series, andmoving objects built on a system running an RVU series to a system running another RVU seriesby means of Expand, FTP, or media such as magnetic tapes.
NOTE: This manual does not list the SPRs needed for BladeCluster Solution interoperability. Forspecific SPRs required for BladeCluster Solution, see the BladeCluster Solution Manual.
These SPRs must be installed on systems running G-series RVUs if you want the functionality it makesavailable through Expand-connected H-series or J-series RVU systems.
Table 13 Interoperability SPRs for G-Series RVU Systems Connected Through Expand to H-Seriesor J-Series RVU Systems
Introduced in this RVUDescriptionProduct NameMinimum SPR
G06.26Required for remote NEWPROCESS ofOCA objects*
TACLT9205D46^ACF
*T9205D46^ACF is required only if you want the functionality it provides.
These SPRs must be installed on systems running H-series RVUs for compatibility and interoperabilitythrough a ServerNet Cluster with systems running J-Series RVUs.
Table 14 Interoperability SPRs for H-Series RVU Systems Connected through ServerNet to J-SeriesRVU Systems
Introduced in this RVUDescriptionProduct NameMinimum SPR
H06.14Required for ServerNet clustering*SNETMONT0294H01^AAW
H06.14Required for ServerNet clustering*SANMANT0502H01^AAW
*For more details, see the ServerNet Cluster Supplement for HP Integrity NonStop BladeSystems. To find out if yourNonStop server supports ServerNet clustering, see the planning guide for your NonStop server.
52 Preparing to Upgrade the Server Software (Preinstallation Tasks)
These specific SPRs must be installed on systems running G-series RVUs for compatibility andinteroperability through a ServerNet Cluster with systems running J-Series RVUs.
Table 15 Interoperability SPRs for G-Series RVU Systems Connected through ServerNet to J-SeriesRVU Systems
Introduced in this RVUDescriptionProduct NameMinimum SPR
G06.31Required for ServerNet clustering*SNETMONT0294G08^AAX
G06.31Required for ServerNet clustering*SANMANT0502G08^AAX
G06.25Required for ServerNet clustering*OSM ServiceConnection Suite
T0682G06^AAA
*For more details, see the ServerNet Cluster Supplement for HP Integrity NonStop BladeSystems. To find out if yourNonStop server supports ServerNet clustering, see the planning guide for your NonStop server.
These SPRs must be installed on systems running G-Series RVUs for compatibility and interoperabilitythrough a ServerNet Cluster with systems running H-Series RVUs.
Table 16 Interoperability SPRs for G-Series RVU Systems Connected through ServerNet to H-SeriesRVU Systems
Introduced in this RVUDescriptionProduct NameMinimum SPR
G06.26Required for ServerNet clustering*SNETMONT0294G08^AAP
G06.26Required for ServerNet clustering*SANMANT0502G08^AAN
G06.25Required for ServerNet clustering*OSM ServiceConnection Suite
T0682G06^AAA
*For more details, see the ServerNet Cluster Supplement for NonStop NS-Series Servers. To find out if your NonStopserver supports ServerNet clustering, see the planning guide for your NonStop server.
These SPRs facilitate software migration and software management operations between nodesrunning G-series RVUs and nodes running H-series and J-series RVUs:
• The T9621D30^ABB, T9674D30^AAM, T9276D30^AAW, and T0448G06^AAA SPRsprovide the option of using a G-series RVU system to construct objects that will ultimately runon an H-series or J-series RVU system. Possible activities that can be performed in the G-seriesRVU system include accelerating objects that will eventually run on an H-Series or J-series RVUsystem. Once the objects have been properly constructed on the G-series RVU system, theycan be moved to the H-Series or J-series RVU system by whatever means preferred, for example,by Expand, FTP, or magnetic tape. For more details, please refer to the H-Series ApplicationMigration Guide.
• T6031G01^ABP provides the option to use DSM/SCM to manage software in an environmentcomposed of systems running different RVU series. The systems need not be connected throughExpand. For more details, refer to the NonStop Software Essentials User's Guide.
• T9617G03^AAY allows you to check the VPROC of H-series and J-Series object files thathave been copied to a G-series RVU system or in situations where a G-series RVU node isused to manage software for a H-series or J-series RVU system. This functionality can also beused to query the VPROC of a remote object file through Expand.
Table 17 SPRs for Software Migration and Software Management Operations Between G-Series,H-Series and J-Series RVU-Based Systems
Introduced in this RVUDescriptionProduct NameMinimum SPR
G06.27Required to recognize 800 filesVPROCT9617G03^AAY
G06.27Required to recognize OCA regionBinderT9621D30^ABB
Install Node Interoperability SPRs 53
Table 17 SPRs for Software Migration and Software Management Operations Between G-Series,H-Series and J-Series RVU-Based Systems (continued)
Introduced in this RVUDescriptionProduct NameMinimum SPR
G06.27Required to recognize OCA regionPDTSHARET9674D30^AAM
G06.27Required to recognize OCA regionAxcelT9276D30^AAW
G06.27Required to prepare TNS code files to runaccelerated on a NonStop NS-seriesplatform
OCAT0448G06^AAA
Released post G06.26and is backwards
Required to enable receiving H-series SUTsand installing and managing software on
DSM/SCMT6031G01^ABP
compatible to G06.21.a NonStop NS-series target system from aAlso, the G02 SPRNonStop S-series host (available to be(installed with G06.27applied to the G06.26 RVU andand later) meets therequirements.
compatible to G06.21). The functions inT6031ABP and T9298AAM are includedin the G02 DSM/SCM and SWID productversion updates released in G06.27 andlater G-series RVUs.
Back Up System InformationTo ensure you always have a backup of your system information, run your system with a mirror of$SYSTEM. When you are loading a new RVU, you can assure a backup of your system by shuttingdown half of $SYSTEM and other important disks, loading the RVU on the other $SYSTEM, verifyingthe RVU and then reviving the other $SYSTEM. Alternatively, or in addition to running your systemwith a mirror of $SYSTEM and loading the RVU as described, create a disk image of $SYSTEMand store it in a safe place so you can physically install and boot the backup disk if needed.
For NonStop BladeSystem NB54000c and NB54000c-cg Ensure the CoreLicense File is Ready for Migration
Obtain and use the CLICVAL tool if you are upgrading a NonStop NB54000c or NB54000c-cgto J06.13. The CLICVAL tool verifies your core license file is ready for migration or upgrade. Formore information, refer to the NonStop BladeSystem Planning Guide or the TACL Reference Manual.
Manually Install the NonStop Software Essentials Server ProductHP recommends use of NonStop Software Essentials instead of the Planner Interface for upgradingyour RVU. In addition to NonStop Software Essentials being the go-forward strategy, the PlannerInterface is not supported on 64-bit NonStop consoles.If you do not have NonStop Software Essentials, see the NonStop Software Essentials Installationand Quick Start Guide for installation procedures.
54 Preparing to Upgrade the Server Software (Preinstallation Tasks)
6 Installing a SUT for This RVU Using NonStop SoftwareEssentials
NOTE: If you do not have NonStop Software Essentials installed, see the NonStop SoftwareEssentials Installation and Quick Start Guide.
Alerts for Installing a SUTDo 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 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 $ZPNSis started and running on the DSM/SCM Target. (See “Create a New Software Revision”(page 58).) The volume where the SYSnn is being placed must be activated as $SYSTEM toinstall the OSS files. See the Open System Services Management and Operations Guide, orif using EasySetup, see the Open System Services Installation Guide.
• Save the configuration database. See “Save the Current Configuration File (CONFxxyy)”(page 45).
• Verify your system operations. See “Verify System Processes” (page 46).
• If necessary, update the system console.
• Obtain a user name and password authorized to use NonStop Software Essentials. See theNonStop Software Essentials User’s Guide for more information about configuring which usersare allowed to use DSM/SCM and which tasks they are permitted to perform.
NOTE: Safeguard aliases are case-sensitive, and they must be entered exactly when youlog onto NonStop Software Essentials.You can add a Safeguard alias anytime Safeguard is running.Before using an existing alias for NonStop Software Essentials, check that Safeguard is started.Aliases are available only while Safeguard is running.
• Pause the hometerm configured for use by DSM/SCM Pathway servers and other processeswhen DSM/SCM is running. The default hometerm is $ZHOME. See the NonStop SoftwareEssentials User’s Guide for more information about the hometerm used by DSM/SCM Pathwayservers.
• For those OSS products that are not managed by DSM/SCM, you must install them manuallyusing PINSTALL or COPYOSS.
Back Up Important Files• If you have already done so, you should back up important files (such as, TMF, NonStop
SQL/MP, NonStop SQL/MX, CLIM, and so forth). See “Back Up Important Files” (page 44).• Drain the spooler and back up spooler control files.
Receive New Software Into the Archive1. Start TMF and DSM/SCM if they are not already running. For example:
> TMFCOM START TMF> VOLUME $dsmscm_vol.ZDSMSCM> RUN STARTSCM
Alerts for Installing a SUT 55
startscmNOTICE: * 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!
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 - *1079* SERVER US-001, NO STATIC SERVERS DEFINED$Z038: TCP TCP-H, STARTED$Z038: TCP TCP-T, STARTED
2. Start HP SIM and then open a NonStop Software Essentials window by selecting the ManageNonStop Software link on the NonStop server Tools & Links tab.
3. When the Logon appears, enter the user ID or alias and password and click Logon.nl
The NonStop Software Essentials home page is displayed.4. Click Receive Software under the Software Installation group on the home page.
The Receive Software Request page appears. For example:
5. In the Receive options group box, do one of, depending on your system environment:• Select Receive only changed files (default)
• Select Receive all files6. Under Software name, select Provided by planner and enter a name for the RVU.7. Click the Input Source tab.8. Select Tape drive.9. From the list, select the tape drive that contains the SUT.10. Click the Scheduling tab. Make the appropriate selections.
56 Installing a SUT for This RVU Using NonStop Software Essentials
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 needsto be mounted. EMS messages are displayed in the EMS Events window displayed byNonStop Software Essentials when you click the system name in the System column inthe table from the Status page. See the above screen shot.
• You can also check the Requests window to ensure that the request is finished. (SelectRequests>Show Requests.) For example:
13. Expand the SUTs node in the navigation tree and monitor the request status page. When therequest completes, the new SUT will appear at the top of the list of SUTs.
14. Keep NonStop Software Essentials open for the next task.
Receive New Software Into the Archive 57
Create a New Software RevisionWhen you create a new software revision, NonStop Software Essentials selects the products in theSUT 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 NonStopSoftware Essentials. These instructions also assume that you have installed OSS. To configure OSSfor the first time, see the Open System Services Installation Guide. For details on modifying aDSM/SCM target, see the NonStop Software Essentials User’s Guide.1. Check that the OSS Root Name Server $ZPNS is running on the Target. The volume where
the SYSnn is being placed must be activated as $SYSTEM to install OSS files. To determinethe server process, issue an SCF STATUS SERVER command or an SCF LISTDEV command.An example of the STATUS SERVER command is:$ADBIT TESTBIT 11> SCF STATUS SERVER $ZPMON.*SCF - T9082H01 - (01MAY05) (15MAR05) - 07/06/2005 08:58:59 System \ATLAS(C) 1986 Tandem (C) 2003 Hewlett Packard Development Company, L.P.
OSS Status SERVER \ATLAS.$ZPMON.*
ServerName State LastError ErrorDetail#ZMSGQ STARTED 0 0#ZPLS STARTED 0 0#ZPNS STARTED 0 0#ZTA00 STARTED 0 0#ZTA01 STARTED 0 0#ZTA02 STARTED 0 0#ZTA03 STARTED 0 0#ZTA04 STOPPED 0 0#ZTA05 STOPPED 0 0#ZTA06 STOPPED 0 0#ZTA07 STOPPED 0 0#ZTA08 STOPPED 0 0#ZTA09 STOPPED 0 0#ZTA10 STOPPED 0 0#ZTA11 STOPPED 0 0#ZTA12 STOPPED 0 0#ZTA13 STOPPED 0 0#ZTA14 STOPPED 0 0#ZTA15 STOPPED 0 0
Total Errors = 0 Total Warnings = 0$ADBIT TESTBIT 12>
2. In NonStop Software Essentials, load the Configuration Revisions page and then select thetarget configuration.
3. Click the Modify button in the Target Maintenance group box.a. Check that the Manage OSS Files option is selected.
58 Installing a SUT for This RVU Using NonStop Software Essentials
b. Click the Output tab to view the default output values.c. Enter the appropriate values in the data fields.
NOTE: The alternate name for the $SYSTEM drive defaults to $FC1 for fibre channeldrives or $SCSI for SCSI drives. If this default has been changed, then the target volumespecified in NonStop Software Essentials for new subvolumes must reflect this change.
4. Click OK to return to the Configuration Revisions page.5. Click the Create or Edit in the New Revision group box.
The new software revision page loads into the work panel and this page lists the products inthe last software revision that was built for the target system. It might take several minutes.a. In the New software revision dialog box, click Edit Revision Notes.b. A Revision Notes text box containing existing revision notes appears.c. Add a description describing the new software revision (such as J06.14 SUT) and click
OK.d. Click on SUTs in the source tree to get the list of SUTs loaded into the source table. Select
the SUT just received into the archive and click Copy to.6. Click Continue when the Confirmation message appears:
Create a New Software Revision 59
If there are any discrepancies between the set of products included in the previous configurationand the set in your new configuration, the popup shown below is displayed. (These productsare removed by default from the system by DSM/SCM during the Build/Apply of the newconfiguration.)
The dialog box lists products installed on the previous revision that are not available on thenew SUT. To retain these products from the current revision into the new revision:
• To include one or more products in the configuration to be built, select the products andclick Continue.
• To include all products, click the check box in the left column header to select all theproducts.The New software revision list now displays the new revision level. For example:
60 Installing a SUT for This RVU Using NonStop Software Essentials
7. Keep NonStop Software Essentials open for the next task.
Build and Apply the New Software RevisionThe Build process creates an activation package containing all the products listed in the newsoftware revision.To avoid disrupting other system activities, schedule the Build to run at night and the Apply to runimmediately after the build. See the NonStop Software Essentials User’s Guide for informationabout scheduling the Build/Apply to run at different times.To build and apply the new software revision:1. If you want to shut down half of $SYSTEM and other mirrored disks before applying the new
RVU or create a disk image of $SYSTEM and store it in a safe place so you can install andboot the backup disk if needed, do so now. For instructions on how to remove a mirrored diskand bring it up later, see the Guardian User's Guide.
2. In the New software revision page, click Build/Apply to display the options for yourBuild/Apply.It might take several minutes for DSM/SCM to assemble the build information. During thistime, the Processing New Revision progress bar is displayed.When the Build information is assembled, the Build/Apply Request page is displayed. Itdisplays default options and assigns a name to the Build/Apply request. For example:
Build and Apply the New Software Revision 61
3. Under Perform steps, select Build, apply & process snapshot.4. 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 thatare currently on your system.
> fileinfo $system.*.osimage
5. Make a note of the new SYSnn. You will specify this SYSnn subvolume when:• Using the VPROC command to verify the location and version of your firmware
• Specifying the location of firmware for a new RVU
• Running ZPHIRNM
• Loading a SUT for this RVU6. Edit Planner instructions to operator text to provide the correct (new) SYSnn number.7. Select the Scheduling, Output, SYSGEN, TSV Locations, and File Placement tabs and configure
as appropriate for your system. (See the NonStop Software Essentials User’s Guide or theonline help for more information about Build/Apply Request options.)
62 Installing a SUT for This RVU Using NonStop Software Essentials
8. (Optional) Confirm that the spooler is active and not 100 percent full before executing theBuild/Apply request. At a TACL prompt, start SPOOLCOM and issue a COLLECT, STATUScommand. For example:
12> spoolcom $spls; collect, status
COLLECT STATE FLAGS CPU PRI UNIT DATA FILE %FULL$S ACTIVE 3 , 1 154 4 $OPS0.SPL.DATA 4
9. In the Build/Apply Request page, click Submit Build/Apply.DSM/SCM runs the Build and Apply steps and displays a Status window, which is automaticallyupdated every five seconds. For example:
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 thisBuild/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, Createsnapshot, and Receive snapshot activities finished. For example:
Build and Apply the New Software Revision 63
• The last message in the EMS Events window shows that the input snapshot finishedsuccessfully.
• The Requests window shows that the request is finished. (Select Requests> Show Requests).11. Exit NonStop Software Essentials.
Print Operator Instructions From the Target Interface (ZPHITI)Print the operator instructions that you edited.1. Enter the following from the DSM/SCM subvolume to display the TI Logon screen:
RUN ZPHITI
DSM Software Configuration Manager TI Logon ==============================================================================
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. 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. 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 and password and press F1 to log on to the Target Interface.The Main Menu appears:
DSM Software Configuration Manager Main Menu ============================================================================== \WARRIOR Prior snapshot 2007-11-09:12:18:44
64 Installing a SUT for This RVU Using NonStop Software Essentials
Selection number: 0
============================================================================== Choose an action by entering the selection number of an item from the list below. ============================================================================== 1 Create system report 2 Create system snapshot 3 Perform target activities 4 Perform audit 5 Perform database verify
9 Enable trace (for support use only)
============================================================================== F1-Select F4-Show Messages F15-Help F16-Return SF16-Exit Ready
3. From the ZPHITI Main Menu, enter 3 (Perform target activities) in the Selection number field,and press F1 to display the Target Menu - Select Target screen.
DSM Software Configuration Manager Target Menu - Select Target ============================================================================== \WARRIOR Prior snapshot 2007-09-20:12:18:44
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
4. In the Selection number field, enter the number corresponding to the logical target to whichyou applied the software (selection 2 in this example), and press F1 to display the TargetMenu - Select Action screen.
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. ============================================================================== 1 Perform/Review apply request 2 Perform backout to S/W Applied on SYS 01 on 2006-09-13:15:44 3 Review operator instructions for the last apply completed.
==============================================================================
Print Operator Instructions From the Target Interface (ZPHITI) 65
F1-Select F15-Help F16-Return SF16-Exit Ready
5. Enter 3 (Review operator instructions for the last apply completed) in the Selection numberfield, and press F1 to display the operator instructions.
6. Enter a printer location in the Print operator instructions field, and press F9 to print the operatorinstructions.An example instruction screen might look like this:
Activation Instructions for \BITDRP BITDRP These are general instructions that were determined from configuration attributes. Refer to the release documentation for detailed information on migrating to this software configuration.
1. Stop all applications. Keep OSS running.2. RUN ZDSMSCM.ZPHIRNM SYS01 (Note: replace nn with correct number)3. Check for $0 EMS messages. Correct any errors indicated in the $0 EMS messages. Do not proceed until this step has been successfully completed.4. Coldload is required.5. Run merge_whatis if ZPHIRNM indicates it is needed.6. Update FIRMWARE. Run OSM (or TSM) to check firmware and perform firmware updates. T2805 MAINTENANCE ENTITY includes firmware changes. T2805 MAINTENANCE ENTITY includes firmware changes. T0287 HALTED STATE SVCS includes firmware changes. T0630 FCSA F/W includes firmware changes. T0287 HALTED STATE SVCS includes firmware changes. T0287 HALTED STATE SVCS includes firmware changes.7. Restart all applications.
7. Press SF16 to exit the Target Interface.In the Activation instructions, you might see information regarding the merge_whatis OSScommand:
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 usedby the OSS shell man, apropos, and whatis commands. You must run the merge_whatiscommand 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 OSSmerge_whatis utility automatically, you can ignore running merge_whatis.
Recovery for Problems Installing This RVU SUT or SPRsIf you receive an error indication in the Requests, Status, or EMS Events windows, you might haveto re-initiate the Build/Apply. See the DSM/SCM Messages Manual to determine the nature andseverity of the problem.
Cancel Pending Build/Apply Requests
NOTE: If you inadvertently navigate away from the Status page, reopen it by clicking on theRequest Name link on the Request List page.
Click the Cancel button on the Request Status page.
66 Installing a SUT for This RVU Using NonStop Software Essentials
The cancel request action takes a few minutes to finish.
NOTE: If you cannot cancel the Build request through NonStop Essentials, use the DSM/SCMTarget Interface (ZPHITI) to cancel the request. See the NonStop Essentials User's Guide and theonline help for more information.
Recovery for Problems Installing This RVU SUT or SPRs 67
7 Installing a SUT for This RVU Using the Planner InterfaceAlerts 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 146).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 $ZPNSis started and running on the DSM/SCM Target. (See “Create a New Software Revision”(page 72).) The volume where the SYSnn is being placed must be activated as $SYSTEM toinstall the OSS files. See the Open System Services Management and Operations Guide, orif using EasySetup, see the Open System Services Installation Guide.
• Save the configuration database. See “Save the Current Configuration File (CONFxxyy)”(page 45).
• Verify your system operations. See “Verify System Processes” (page 46).
• If necessary, update the system console.
• Obtain a user name and password authorized to use the DSM/SCM Planner Interface. Seethe DSM/SCM User’s Guide for more information about configuring which users are allowedto use DSM/SCM and which tasks they are permitted to perform.
NOTE: Safeguard aliases are case-sensitive, and they must be entered exactly when youlog onto DSM/SCM.You can add a Safeguard alias anytime Safeguard is running.Before using an existing alias for DSM/SCM, check that Safeguard is started. Aliases areavailable only while Safeguard is running.
• Pause the hometerm configured for use by DSM/SCM Pathway servers and other processeswhen DSM/SCM is running. The default hometerm is $ZHOME. See the DSM/SCM User’sGuide for more information about the hometerm used by DSM/SCM Pathway servers.
• For those OSS products that are not managed by DSM/SCM, you must install them manuallyusing PINSTALL or COPYOSS.
Back Up Important Files• If you have already done so, you should back up important files (such as, TMF, NonStop
SQL/MP, NonStop SQL/MX, CLIM, and so forth). See “Back Up Important Files” (page 44).• Drain the spooler and back up spooler control files.
Receive New Software Into the Archive1. Start TMF and DSM/SCM if they are not already running. For example:
> TMFCOM START TMF> VOLUME $dsmscm_vol.ZDSMSCM> RUN STARTSCM
startscmNOTICE: * 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!
68 Installing a SUT for This RVU Using the Planner Interface
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 - *1079* SERVER US-001, NO STATIC SERVERS DEFINED$Z038: TCP TCP-H, STARTED$Z038: TCP TCP-T, STARTEDStart the DSM/SCM Planner Interface
2. Select Start>Programs>dsm_scm>DSMSCM.3. When the Logon dialog box appears, enter the user ID or alias and password and click OK.
The Planner Interface screen displays two dialog boxes:
• The Software in Archive dialog box lists the software that is currently in the DSM/SCMArchive.
• The Configuration Revisions dialog box lists the current software revisions.4. In the Software in Archive dialog box, click Receive software.
The Receive Software Request dialog box appears. For example:
5. In the Receive Options group box, do one of, depending on your system environment:• Select Receive only changed files (default)
• Select Receive all files (recommended for the new RVU)6. Under Software name, select Provided by planner and enter a name for the RVU.7. In the Options group box, click Input source.
The Request Source Options dialog box appears.8. Select Tape drive.
Receive New Software Into the Archive 69
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 andclick 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. For example:
70 Installing a SUT for This RVU Using the Planner Interface
• EMS event messages to see if a cartridge on a nonautoloading drive of the SUT needsto 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 eventsfrom the Status window
◦ You can also check the Requests window to ensure that the request is finished. (SelectRequests>Requests list.) For example:
Receive New Software Into the Archive 71
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 RevisionWhen you create a new software revision, DSM/SCM selects the products in the SUT that arelicensed 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 are in the Planner Interface Configuration Revisions window.These instructions also assume that you have installed OSS. To configure OSS for the first time,see the Open System Services Installation Guide. For details on modifying a DSM/SCM target,see the DSM/SCM User’s Guide.1. Check that the OSS Root Name Server $ZPNS is running on the Target. The volume where
the SYSnn is being placed must be activated as $SYSTEM to install OSS files. To determinethe server process, issue an SCF STATUS SERVER command or an SCF LISTDEV command.An example of the STATUS SERVER command is:
$ADBIT TESTBIT 11> SCF STATUS SERVER $ZPMON.*SCF - T9082H01 - (01MAY05) (15MAR05) - 07/06/2005 08:58:59 System \ATLAS(C) 1986 Tandem (C) 2003 Hewlett Packard Development Company, L.P.
OSS Status SERVER \ATLAS.$ZPMON.*
ServerName State LastError ErrorDetail#ZMSGQ STARTED 0 0#ZPLS STARTED 0 0#ZPNS STARTED 0 0#ZTA00 STARTED 0 0#ZTA01 STARTED 0 0#ZTA02 STARTED 0 0#ZTA03 STARTED 0 0#ZTA04 STOPPED 0 0#ZTA05 STOPPED 0 0#ZTA06 STOPPED 0 0#ZTA07 STOPPED 0 0#ZTA08 STOPPED 0 0#ZTA09 STOPPED 0 0#ZTA10 STOPPED 0 0#ZTA11 STOPPED 0 0#ZTA12 STOPPED 0 0#ZTA13 STOPPED 0 0#ZTA14 STOPPED 0 0#ZTA15 STOPPED 0 0
Total Errors = 0 Total Warnings = 0$ADBIT TESTBIT 12>
1. In the DSM/SCM Planner Interface, in the Configuration Revisions dialog box, select the targetconfiguration.
2. Select Maintain→Target Maintenance→Modify.a. Check that the Manage OSS Files option is selected.
72 Installing a SUT for This RVU Using the Planner Interface
b. Click Output to view the default output values.c. Enter the appropriate values in the data fields.
NOTE: The alternate name for the $SYSTEM drive defaults to $FC1 for fibre channeldrives or $SCSI for SCSI drives. If this default has been changed, then the target volumespecified in the Planner Interface for new subvolumes must reflect this change.
d. Click OK. DSM/SCM returns you to the Target Information dialog box.3. Click OK to return to the Configuration Revisions dialog box.4. Click OK to return to the Planner Interface.5. Select New software revision.
DSM/SCM opens a New software revisions dialog box that lists the products in the lastsoftware revision that was built for the target system. It might take several minutes for thedialog box to appear.a. In the New software revision dialog box, click Edit revision notes.b. A Revision Notes text box containing existing revision notes appears.c. Add a description describing the new software revision (such as J06.14 SUT) and click
OK.d. In the Software in Archive window, select the RVU SUT that was just received into the
archive and click Copy to.
Create a New Software Revision 73
6. Click Continue when the Confirmation message appears:
If there are any discrepancies between the set of products included in the previous configurationand the set in your new configuration, a warning message appears listing any products missingin the current configuration that were present in the previous configuration. (These productsare 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. If this isthe case, install them using PINSTALL/COPYOSS. See the appropriate OSS manuals for usingPINSTALL and COPYOSS.The Non SUT Products screen might appear:
The dialog box lists products installed on the previous revision that are not available on thenew SUT. To retain these products from the current revision into the new revision:
• 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.nn). For example:
74 Installing a SUT for This RVU Using the Planner Interface
7. Keep the Planner Interface open for the next task.
Build and Apply the New Software RevisionThe Build process creates an activation package containing all the products listed in the newsoftware revision.To avoid disrupting other system activity, schedule the Build to run at night and the Apply to runimmediately after the build. See the DSM/SCM User’s Guide for information about scheduling theBuild/Apply to run at different times.To build and apply the new software revision:1. If you want to shut down half of $SYSTEM and other mirrored disks before applying the new
RVU or create a disk image of $SYSTEM and store it in a safe place so you can install andboot the backup disk if needed, do so now. For instructions on how to remove a mirrored diskand bring it up later, see the Guardian User's Guide.
2. In the New software revision dialog box, click Build/Apply to display the options for yourBuild/Apply.It might take several minutes for DSM/SCM to assemble the build information. During thistime, the Build/Apply Request dialog box options and commands are dimmed and unavailable.When the Build information is assembled, the Build/Apply Request dialog box is refreshed.It displays default options and assigns a name to the Build/Apply request. For example:
Build and Apply the New Software Revision 75
3. Under Perform steps, select Build, apply & process snapshot.4. 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 thatare currently on your system.
> fileinfo $system.*.osimage
5. Make a note of the new SYSnn. You will specify this SYSnn subvolume when:• Using the VPROC command to verify the location and version of your firmware
• Specifying the location of firmware for a new RVU
• Running ZPHIRNM
• Loading a SUT for this RVU6. Click Edit instructions to display the Planner Instructions dialog box.7. Edit the instructions to provide the correct (new) SYSnn number, and then click OK.
The Planner Instructions box closes.8. Select the Scheduling, Output, SYSGEN, TSV Location, and File Placement options and
configure as appropriate for your system. (See the DSM/SCM User’s Guide or the online helpfor more information about Build/Apply Request options.) When completed, click OK.
76 Installing a SUT for This RVU Using the Planner Interface
9. (Optional) Confirm that the spooler is active and not 100 percent full before executing theBuild/Apply request. At a TACL prompt, start SPOOLCOM and issue a COLLECT, STATUScommand. For example:
12> spoolcom $spls; collect, status
COLLECT STATE FLAGS CPU PRI UNIT DATA FILE %FULL$S ACTIVE 3 , 1 154 4 $OPS0.SPL.DATA 4
10. In the Build/Apply Request dialog box, click OK.
Build and Apply the New Software Revision 77
DSM/SCM runs the Build and Apply steps and displays a Status window, which is automaticallyupdated at regular intervals. For example:
78 Installing a SUT for This RVU Using the Planner Interface
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 hostdatabase:
• The Request activity summary in the Status window shows that the Build, Apply, Createsnapshot, and Receive snapshot activities finished. For example:
Build and Apply the New Software Revision 79
• The last message in the EMS Events window shows that the input snapshot finishedsuccessfully.
• 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. Enter the following from the DSM/SCM subvolume to display the TI Logon screen:
RUN ZPHITI
DSM Software Configuration Manager TI Logon ==============================================================================
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. 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. T6031H01 11NOV2007
80 Installing a SUT for This RVU Using the Planner Interface
(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 TargetInterface.The Main Menu appears:
DSM Software Configuration Manager Main Menu ============================================================================== \WARRIOR Prior snapshot 2007-11-09:12:18:44
Selection number: 0
============================================================================== Choose an action by entering the selection number of an item from the list below. ============================================================================== 1 Create system report 2 Create system snapshot 3 Perform target activities 4 Perform audit 5 Perform database verify
9 Enable trace (for support use only)
============================================================================== F1-Select F4-Show Messages F15-Help F16-Return SF16-Exit Ready
3. From the ZPHITI Main Menu, enter 3 (Perform target activities) in the Selection number field,and press F1 to display the Target Menu - Select Target screen.
DSM Software Configuration Manager Target Menu - Select Target ============================================================================== \WARRIOR Prior snapshot 2007-09-20:12:18:44
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
4. In the Selection number field, enter the number corresponding to the logical target to whichyou applied the software (selection 2 in this example), and press F1 to display the TargetMenu - Select Action screen.
Print Operator Instructions From the Target Interface (ZPHITI) 81
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. ============================================================================== 1 Perform/Review apply request 2 Perform backout to S/W Applied on SYS 01 on 2006-09-13:15:44 3 Review operator instructions for the last apply completed.
============================================================================== F1-Select F15-Help F16-Return SF16-Exit Ready
5. Enter 3 (Review operator instructions for the last apply completed) in the Selection numberfield, and press F1 to display the operator instructions.
6. Enter a printer location in the Print operator instructions field, and press F9 to print the operatorinstructions.An example instruction screen might look like this:
Activation Instructions for \BITDRP BITDRP These are general instructions that were determined from configuration attributes. Refer to the release documentation for detailed information on migrating to this software configuration.
1. Stop all applications. Keep OSS running.2. RUN ZDSMSCM.ZPHIRNM SYSnn (Note: replace nn with correct number)3. Check for $0 EMS messages. Correct any errors indicated in the $0 EMS messages. Do not proceed until this step has been successfully completed.4. Coldload is required.5. Run merge_whatis if ZPHIRNM indicates it is needed.6. Update FIRMWARE. Run OSM (or TSM) to check firmware and perform firmware updates. T2805 MAINTENANCE ENTITY includes firmware changes. T2805 MAINTENANCE ENTITY includes firmware changes. T0287 HALTED STATE SVCS includes firmware changes. T0630 FCSA F/W includes firmware changes. T0287 HALTED STATE SVCS includes firmware changes. T0287 HALTED STATE SVCS includes firmware changes.7. Restart all applications.
7. Press SF16 to exit the Target Interface.In the Activation instructions, you might see information regarding the merge_whatis OSScommand:
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 usedby the OSS shell man, apropos, and whatis commands. You must run the merge_whatiscommand once against each directory that contains the man page files to be used.
82 Installing a SUT for This RVU Using the Planner Interface
You will run merge_whatis after using ZPHIRNM. If you have OSS configured to run the OSSmerge_whatis utility automatically, you can ignore running merge_whatis.
Recovery for Problems Installing This RVU SUT or SPRsIf you receive an error indication in the Requests, Status, or EMS Events windows, you might haveto re-initiate the Build/Apply. See the DSM/SCM Messages Manual to determine the nature andseverity of the problem.
Cancel Pending Build/Apply Requests
NOTE: If you inadvertently close the Status dialog box, reopen it by selecting Requests→ Requestslist and then double-clicking the request.
1. Select the request to be canceled.2. 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, usethe DSM/SCM Target Interface (ZPHITI) to cancel the request. See the DSM/SCM User’sGuide and online help.
Recovery for Problems Installing This RVU SUT or SPRs 83
8 Running ZPHIRNMDuring 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 runningprograms.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 becomeobsolete when the new files are renamed.
• Rename new files, which have fabricated names, with their actual names.Warning, error, and completion messages are written to a log file if you choose to create one.Error and completion messages are also displayed in the terminal-emulation window.After ZPHIRNM has completed renaming all OSS and Guardian files, it will run ZMODGP if itexists in the SYSnn being activated and if:
• The configuration being activated contains a ZCNFDEFS TSV:
104 Processing TSV $SYSTEM.ZCNFDEFS Mapfile ZMP0007N (102)
• One or more of the ZcccGP files in the ZCNFDEFS TSV are new or changed (as comparedto the last configuration activated). If none of the ZcccGP files change, ZMODGP is not run.
Alerts• Back up copies of HP NonStop TCP/IP configuration files in the ZTCPIP subvolume 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 runningZPHIRNM.
• You must have rename (purge) access to all files being renamed. Run ZPHIRNM as the superID (255,255).
• If you are connected to an Expand network, you might see a message stating that the NonStopSQL file, ZZSQLCI2, was not renamed during ZPHIRNM. However, on further examinationof the log file, you might find that ZPHIRNM did finally rename the file, in which case youcan ignore the error message and continue.
• If you are using DSM/SCM to manage OSS files, ZPHIRNM notifies you if and when to runthe merge_whatis command. Run merge_whatis after loading the new system.
• If ZPHIRNM is run in PREVIEW mode, ZMODGP is run in TRIAL mode. However, any errorsin the new and changed files will not be discovered in preview or trial mode because ZPHIRNMin preview mode does not actually rename the files. Therefore, ZMODGP will not be runagainst the same files as when the real file activation is done.
• Prior to performing an RVU migration, install DSM/SCM SPR T6031H02^ACJ or later. SeeHotstuff HS03058 for more information.
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
84 Running ZPHIRNM
• DNSCACHE
• DNSHOSTS
• DNSLOCAL
• DNSREV
• DNREVBAK
• HOSTS
• NETWORKS
• PORTCONF
• PROTOCOL
• RESCONF
• SERVICES
• SMTPCONFThe 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 ApplicationsBefore running ZPHIRNM:1. Stop DSM/SCM if it is still running. For example:
> VOLUME $dsmscm_vol.ZDSMSCM> Run STOPSCMSTOP CNFGINFO server process $ZPHCSTOP DSM/SCM Pathway system $YPHIPATHCOM $YPHI;SHUTDOWN !,WAIT$Z02H: TCP TCP-H, STOPPED$Z02H: TCP TCP-T, STOPPEDSTOP DSM/SCM Alternate EMS Collector $ZPHI
where $dsmscm_vol is the DSM/SCM volume.
2. Stop all other applications, except for TMF and the OSS file system.The planning guides for the NonStop systems contain detailed information on stopping applications,devices, and processes in an orderly fashion.
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:
Stop Applications 85
1. Use the SPOOLCOM;COLLECT $collector-process, LISTOPENS command to identifyprocesses that currently have jobs open.
2. Use the SPOOLCOM;JOB (STATE PRINT) command to determine which jobs are currentlyprinting.
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 collectionor printing (new opens are rejected with a file-system error 66—device downed). Each collectorstops when it has no more open jobs. Each print process finishes printing active jobs and thenstops.After all collectors and print processes have stopped, the supervisor process stops itself. The spoolerenters the dormant state, ready to be warm started.
CAUTION: Never use the TACL STOP command to halt the spooler. The control file can becorrupted during the next warm start or rebuild.
For more information on draining the spooler, see Support Note S99086, NSK Spooler—Migrationand Draining Instructions and in the Spooler Utilities Reference Manual.
Back Up the Spooler Control FilesWhile the spooler environment is closed, back up the spooler control files to render a knowndatabase from which you recover in case of a catastrophic spooler failure. Make sure that youdrain the spooler:
BACKUP/OUTSPLBKUP/$TAPE,($SYSTEM.SPOOLER.*,$DATA01.SPOOLER.DATA),LISTALL
ZPHIRNMDuring the Build/Apply phase, DSM/SCM places product files in their subvolumes with temporary(fabricated) file names so that the new file names do not conflict with the file names of currentlyrunning programs. The ZPHIRNM program renames files that currently have actual file names withfabricated names and renames new files, which have fabricated names, with their actual names.ZPHIRNM is run from the DSM/SCM subvolume.
Using ZPHIRNM PREVIEW ModeYou can do a preview run of ZPHIRNM to check that the target subvolumes (TSVs) and associatedmap files are consistent. Running ZPHIRNM in PREVIEW mode simulates the ZPHIRNM processwithout actually updating files or activating the configuration. In PREVIEW mode, ZPHIRNM indicateswhether TMF needs to be up when running ZPHIRNM. For example, if no SQL program files needrunning, TMF is not required to be running along with the ZPHIRNM program.If ZPHIRNM is run in PREVIEW mode, ZMODGP will be run in TRIAL mode. The new ZcccGP fileswill be named ZFBccncc, but cannot be easily distinguished from non-ZcccGP files also namedZFBccncc.Example of ZPHIRNM:
Statistics:
TSVs: TSVs in new configuration .................. 129 TSVs in old configuration .................. 130 TSVs in new configuration only ............. 0 TSVs in old configuration only ............. 1 TSVs shared by new and old configurations .. 129
TSVs processed in new config ............... 129 TSVs processed in old config (obsolete) .... 1
86 Running ZPHIRNM
Files Processed:
Files processed in new configuration ........................... 4038 Files processed in new configuration only ...................... 0 Files processed in old configuration only ...................... 9 Files processed that are shared by new and old configuration ... 4038 Files processed & unchanged between new and old configuration .. 4038 Files processed in obsolete TSVs ............................... 14 Files renamed from real name to fabricated name ................ 23 Files renamed from fabricated name to real name ................ 0 Files renamed from real name to fabricated (ZPG) name .......... 0 Files renamed from fabricated name to fabricated (ZPG) name .... 0
------- Total Number of files renamed .................................. 23
Number of files renamed back during undo processing ............ 0
Generic Process MODification(ZMODGP) is not required because no ZcccGP filesin the $SYSTEM.ZCNFDEFS TSV have changed.
Process Time:
Start ....... 1/29/08 16:43:20 End ......... 1/29/08 16:43:37 Elapsed ..... 0:00:16
Errors & Warnings:
Total Rename Errors ..... 0 Total Rename Warnings ... 0
ZPHIRNM for $SYSTEM($DRP07).SYS04 finished successfully
PREVIEW mode also reveals most errors that ZPHIRNM would encounter if it were run. If errorsare revealed, you can evaluate and correct them interactively.The syntax for running ZPHIRNM in PREVIEW mode is (from the DSM/SCM subvolume):
> RUN ZPHIRNM [$vol.]SYSnn , PREVIEW [STRICT] [,option] ...
If you enter a RUN ZPHIRNM command with no arguments, ZPHIRNM help text displays informationabout PREVIEW mode. For more information, see the NonStop Software Essentials User’s Guide.
Steps for Running ZPHIRNM1. At a TACL prompt, enter this command from the DSM/SCM subvolume:
> RUN ZPHIRNM $vol.SYSnn
where:
• $vol specifies the default current system load volume, usually $SYSTEM.
• SYSnn specifies the subvolume to which you just applied software. The SYSnn subvolumemust match the activation SYSnn that you specified earlier during the Build/Apply phase.
2. When asked if you want to use a log file with the session, enter Y.3. When prompted, enter a file name for the log file:
6> run zphirnm $system.sys00
DSM/SCM Utility - ZPHIRNM - T6031H01 - (11NOV2007)Copyright Hewlett Packard Development Company L.P. 1993-2004
ZPHIRNM 87
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 diskfile 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 /usr/share/man/whatis
b. After reviewing the displayed file, exit by entering the letter q at the percentage (%)prompt.
c. Repeat Steps a. and b. for the whatis_old file.
Verify That ZPHIRNM Ran Successfully1. Review the log file.2. If ZPHIRNM did not run successfully, correct whatever problems occurred and run it again.
Two types of error and warning messages are issued during the renaming process:
• If a fatal error occurs, ZPHIRNM immediately issues an error message and stops.
• If a nonfatal error occurs, ZPHIRNM issues an error message and attempts to restore thesubvolume it is currently processing to its original state. A nonfatal error is one that affectsprocessing only for a single subvolume.
◦ If the subvolume is successfully restored, ZPHIRNM continues with the next subvolume.
◦ If the subvolume cannot be restored, ZPHIRNM issues an additional error messageand continues with the next subvolume.
◦ If the subvolume was successfully processed, you can ignore warning messages.See the DSM/SCM User’s Guide for troubleshooting procedures and the DSM/SCMMessages Manual for a complete list of ZPHIRNM messages.
88 Running ZPHIRNM
9 Loading This RVUThis step loads this RVU into the memory of each processor.
NOTE: For detailed information on performing a system load of a NonStop system, see theNonStop 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 18 System Load Paths in Order of Use for FCDM-Load
Over ServerNet FabricTo ProcessorData Travels FromDescriptionLoad Path
X0$SYSTEM-PPrimary1
Y0$SYSTEM-PPrimary2
X0$SYSTEM-BBackup3
Y0$SYSTEM-BBackup4
X0$SYSTEM-MMirror5
Y0$SYSTEM-MMirror6
X0$SYSTEM-MBMirror backup7
Y0$SYSTEM-MBMirror backup8
X1$SYSTEM-PPrimary9
Y1$SYSTEM-PPrimary10
X1$SYSTEM-BBackup11
Y1$SYSTEM-BBackup12
X1$SYSTEM-MMirror13
Y1$SYSTEM-MMirror14
X1$SYSTEM-MBMirror backup15
Y1$SYSTEM-MBMirror backup16
An FCDM-load attempts to load the system from a system disk in the disk drive enclosure connectedto IOAM enclosure group 110:
Disk DriveEnclosure
FCSAIOAM
BayShelfSACSlotModuleGroupPath
11112110Primary
11113110Backup
11213110Mirror
11212110Mirror Backup
89
Table 19 System Load Paths in Order of Use for CLIM-Attached-Load
Over ServerNet FabricTo ProcessorData Travels FromDescriptionLoad Path
X0$SYSTEM-PPrimary1
Y0$SYSTEM-PPrimary2
Y0$SYSTEM-BBackup3
X0$SYSTEM-BBackup4
X0$SYSTEM-MMirror5
Y0$SYSTEM-MMirror6
Y0$SYSTEM-MBMirror backup7
X0$SYSTEM-MBMirror backup8
Y1$SYSTEM-PPrimary9
X1$SYSTEM-PPrimary10
X1$SYSTEM-BBackup11
Y1$SYSTEM-BBackup12
Y1$SYSTEM-MMirror13
X1$SYSTEM-MMirror14
X1$SYSTEM-MBMirror backup15
Y1$SYSTEM-MBMirror backup16
A CLIM-attached-load attempts to load the system from a system disk in the NonStop Storage CLIMsconnected to a ServerNet switch.CLIM-attached-load for system with 2 CLIMs over $SYSTEM:
ServerNet Switch
Mirror LUNPrimary LUNFiberConnectorSlotModuleGroupPath
N/A1011352100Primary
N/A1013352100Backup
201N/A3352200Mirror
201N/A1352100Mirror Backup
CLIM-attached-load for a system with four CLIMs over $SYSTEM:
ServerNet Switch
Mirror LUNPrimary LUNFiberConnectorSlotModuleGroupPath
N/A1011352100Primary
N/A1011452100Backup
101N/A3452100Mirror
101N/A3352100Mirror Backup
You can configure additional alternate system disks. To create an alternate system disk, see thehardware installation manual for your system. Then use OSM to make the disk available in theConfiguration drop-down menu in the System Load dialog box. The alternative system disks are
90 Loading This RVU
displayed in the Attributes tab under the System object in the OSM Service Connection and arealso displayed in the OSM Low-Level Link System Load dialog box in the Configuration shortcutmenu.
AlertsBefore performing a system load:
• Before halting the processors, stop applications that are still running, including TMF.
NOTE: To stop TMF, at a TACL prompt, enter:TMFCOM STOP TMF
The NonStop Operations Guide contains detailed information on the best methods for stoppingapplications, devices, and processes.
• Ensure that sufficient swap file space is available for the installation. Either use NSKCOM toensure that there is at least one KMSF swapfile on $SYSTEM for each of CPU 0 and CPU 1,or ensure that there is more than 40MB of free space on $SYSTEM.There are several ways to create additional free space on $SYSTEM, including:
◦ Delete all existing zlog*.* files
◦ Delete all existing *.zzsa* files
• Do not close the System Load Startup dialog box while startup is in progress. If you attemptto close the dialog box, a message dialog box appears notifying you that the system startupprocess will be stopped if you continue.
• If you stop a system startup before it has finished, the state of your system will be unpredictable.You might need to perform another system startup to enable the system to resume normaloperation.
• If you must stop the system startup process, click Abort. (The abort process should take effectwithin 30 seconds.)
• In the System Load dialog box, either select all four disk paths, or check that the selected diskpath is correct. If you do not select all four or select the incorrect disk path, the system doesnot load properly.
• If you have problems performing a system load, see the NonStop Operations Guide, Chapter15.
Perform Updates
1. Before Halting the Processors
A. When Upgrading From a J06.04 or Earlier RVU: Removing #ZPLSWhen upgrading to this RVU from a J06.04 or earlier RVU, before halting the processors, youmust remove the SERVER #ZPLS entry from the OSS subsystem maintenance file OSSINFIL on allsystems with OSS installed. The simplest way to do this is to use the TEDIT utility to change theSERVER #ZPLS entry to a comment, as follows:TEDIT $SYSTEM.ZOSSINS.OSSINFIL
Then changeSERVER #ZPLS
to* SERVER #ZPLS
Alerts 91
Failure to do this can result in an error during startup of OSS. This error occurs on systems withpre-T0585H01.
B. When Upgrading From a J06.05 or Earlier RVU: CLIM SoftwareCLIMs configured with the CLIM software released with J06.05 or J06.04 are not compatible withJ06.06 and later RVUs. Performing the CLIM upgrade when the processors are halted, as shownin this procedure, ensures the CLIM and host system will be compatible when you restart the system.For migrations from J06.05 or J06.04, do not perform an online upgrade to the CLIMs before theRVU upgrade. Preliminary online CLIM upgrades are only supported for J06.06 and later J-seriesRVUs.
2. Halt the Processors1. Log on to the OSM Low-Level Link.2. On the toolbar, click Processor Status to display the Processor Status dialog box.3. Under Processor Status, select all processors.4. From the Processor Actions list, select Halt.5. Click Perform action.6. Click OK when asked “Are you sure you want to do Halts?”7. When the Action Status box confirms that all processors have halted, close the Processor Status
dialog box.
3. (Optional): Update System Firmware Using HP SUMThe system firmware is bundled along with HP SUM. Download the required system firmware fromhp.com. (This applies to NonStop NS2200 series, NS2100, and NonStop BladeSystem NB54000cservers only and is not always required. See the NonStop Firmware Matrices for the link and forinformation about required levels.) The self-extractable exe file contains HP SUM and the systemfirmware. Once extracted, double click on hpsum.exe.
4. (Optional): Update HSS Firmware
NOTE: To upgrade HSS for all NonStop systems running J-series software except for NS2000,install the necessary upgrade onto the console from the NonStop System Console Installer DVD,then use the OSM Low-Level Link as follows.
If necessary, while the processors are halted, update the HSS firmware by hard resetting allprocessor blades as follows:
NOTE: If you did step 3, you can skip this step because the processor blades have been powercycled.
NOTE: This step is not necessary for NS2000-series or NS2100 servers.
1. Log on to the OSM Low-Level Link.2. On the toolbar, click Processor Status to display the Processor Status dialog box.3. Under Processor Status, select all processors.4. From the Processor Actions list, select Hard Reset.5. Click Perform action.6. Click OK when asked “Do you really want to perform a Hard Reset on the selected
processor(s)?”7. When the Action Status box confirms that all processors have been reset, close the Processor
Status dialog box.
92 Loading This RVU
5. (Required for Upgrade to J06.14) Reset the System FirmwareWhen upgrading to J06.14 from an earlier RVU, you must perform a hard reset on all processorblades.To accomplish a hard reset on all processor blades, perform all the steps described in “4. (Optional):Update HSS Firmware ” (page 92) using OSM Low-Level Link.
NOTE: You must perform this operation on any system moving to the J06.14 RVU, includingNonStop BladeSystems, NS2000, and NS2200 series servers.
NOTE: You do not need to perform this operation again if you already performed the stepsdescribed in “3. (Optional): Update System Firmware Using HP SUM” (page 92) on all processorblades or if you performed the hard resets specified in “4. (Optional): Update HSS Firmware ”(page 92).
NOTE: You do not need to perform this operation again during subsequent system loads, providedthe previously executing RVU was at least J06.14.
6. Upgrade the CLIM SoftwareIf you have not upgraded the CLIMs online before performing this RVU upgrade, upgrade the CLIMsoftware on each CLIM now. See Upgrading CLIM Software Using OSM Low-Level Link in theCluster I/O Protocols (CIP) Configuration and Management Manual.
7. Loading the SystemIf the automatic system load is not successful using one load path, the system load task attemptsto use another path and keeps trying until all possible paths have been used or the system load issuccessful. Eight paths are available for loading.The CIIN file is automatically invoked after the first processor is loaded. The CIIN file contains theTACL RELOAD * command, which loads the remaining processors.For details on load paths, see the hardware installation manual for your system.
Steps for Loading the SystemA normal system load consists of loading the operating system from disk into the memory ofprocessor 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. 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, oran alternate system volume.
a.
b. If you are using non-default locations for the $SYSTEM volume:• For FCDM-load: Set the controller location and disk partition location using the Disk
Configuration Dialog boxes in the OSM Low-Level Link.• For a CLIM-Attached-Load: Change the CLIM name, CLIM location, and disk location
using the OSM Low-Level Link System Load dialog box and CLIM Attached DiskConfiguration dialog boxes as needed.
3. In the SYSnn box, enter nn, which is the number of the system subvolume that contains theversion 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.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.
Perform Updates 93
4. Under Configuration, ensure that all the check boxes for all paths are selected.5. Click Start System. The system load begins.
If you want to stop the load process, click Abort in the System Load dialog box. You mightwait up to 30 seconds before the abort takes effect.
CAUTION: Do not close the System Load dialog box while startup is in progress. If youattempt to close the dialog box, an OSM message box indicates that the system startup processwill be stopped if you continue. If you stop a system startup before the operation finishes, thestate of your system cannot be predicted. You might need to perform another system startupto enable the system to resume normal operation.
The Details dialog box displays Logon successful and Read configurationspassed (FCDM example):
The following example shows the same dialog box for a CLIM-attached load:
94 Loading This RVU
Start the MR-Win6530 terminal emulator and open one window each for the CNSL sessiondisplay and the CLCI session display.If one or more of the startup event stream windows or startup TACL windows does not launchon the system console after a few minutes (5 to 8 minutes), abort system startup, close theOSM Low-Level Link, reboot the system console, and restart the system load using the OSMLow-Level Link again.
6. Monitor the system startup process. Messages indicating the progress and completion of thesystem load, and the reload of processors indicated in the CIIN file, appear in these displaylocations on the system console.When the system load is complete (the operating system is loaded successfully into the memoryof processor 0 or processor 1), the Detailed box on the System Load dialog box displays:
SYSTEM STARTUP COMPLETE, NSK RUNNING ON PROCESSOR n
7. If the system load fails, look for halt codes or messages displayed in the Detailed box onSystem Startup dialog box. For recovery procedures, see the Processor Halt Codes Manualor Operator Messages Manual.
Perform Updates 95
Completing the System Load (If Necessary)Loading the processors with the CIIN file is usually automatic. However, if the operating systemloaded successfully into processor 0 or processor 1, but the commands in the CIIN file do notreload 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. To load an individual processor or processors, enter:
> RELOAD nn
where nn is the processor number of the processor you want to reload.If the reload is initiated successfully, this message appears in a startup TACL window on thesystem console screen:
PROCESSOR RELOAD: nn
For complete syntax, considerations, and examples of the TACL RELOAD command, see theTACL Reference Manual.
Verifying That the System Is StartedVerify that each processor is running the operating system:1. Select Summary>Processor Status.
The Processor Status dialog box should show each processor to be Executing NonStop OS.
2. Close the Processor Status dialog box.
96 Loading This RVU
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.
Updating Firmware (If Necessary)Update the following firmware as necessary:• FCSA firmware
• G4SA firmware
• For any additional Server Blade firmware updates (For any additional firmware updates, theupdate procedures may vary based on the system type. See the documentation specific toyour Nonstop system for detailed information.)
• Any additional Blade firmware, if applicable to your system
• ServerNet Adapter firmware
• ServerNet Clustering firmware
• c7000 enclosure firmware, including the Onboard Administrator (OA) firmware, if applicableto your system. See the NonStop Firmware Matrices document for the minimum requiredversion for this RVU.
• c7000 enclosure ServerNet Switch firmware (ME and ME FPGA), if applicable to your system
• IOAM ServerNet Switch firmware (ME and ME FPGA), if applicable to your system
• VIO enclosure firmware (ME and FPGA), if applicable to your system
• S-series interoperability firmware (Service Processor and Service Processor B), if applicableto your system
• SWAN/SWAN2 Concentrator firmware
• SS7 controller firmware, if applicable to your system
• CLIM firmware, if your system has CLIMs attachedSee the CLuster I/O Module (CLIM) Software Compatibility Reference for details.See Chapter 2: “Managing Microcode and Firmware” for a description of the firmware installationprocedure.To find out what firmware is required for your system, see the appropriate planning guide.
Perform Updates 97
10 Resuming Normal OperationsRevive the Down Half of the Mirrored Disk
If you shut down half of $SYSTEM and other mirrored disks before applying the new RVU, revivethe disks now. For instructions on how to bring up the downed half of a mirrored disk, see theGuardian User's Guide.
Validate Your Core LicenseFor NB54000c and NB54000c-cg systems, use the OSM guided procedure Read Core Licenseand verify that the license information is correct for your system.
Start System ApplicationsYou can now start your application software. Follow your site’s procedures for executing the systemconfiguration and startup (command) files to accomplish this.DSM/SCM is often started automatically by a system command file. If not, you must start it manuallyas described next.
Before Starting DSM/SCM
Initialize SQL for NonStop SQL/MP1. Check that TMF is started:
> TMFCOM STATUS TMF
2. Save a copy of the existing ZZSQLCI2 file on the $SYSTEM disk. For example:
> FUP DUP $SYSTEM.SYSTEM.ZZSQLCI2,$SYSTEM.BKUPZSQL.*, SAVEALL
3. Enter:
> SQLCI INITIALIZE SQL; EXIT;
4. Copy the ZZSQLCI2 file saved previously back to the $SYSTEM disk. For example:
> FUP DUP $SYSTEM.BKUPZSQL.ZZSQLCI2, $SYSTEM.SYSTEM.*, SAVEALL
NOTE: ZZSQLCI2 is a temporary file that contains the SQLCI2 program. SQLCI2 is theprocess through which the NonStop SQL/MP conversational interface (SQLCI) communicateswith the NonStop SQL/MP executor to request various functions. After SQL initialization iscomplete, ZZSQLCI2 is renamed and becomes the permanent SQLCI2 program.HP recommends that you always have a current backup copy of the$SYSTEM.SYSTEM.ZZSQLCI2 file in case you need to initialize SQL later for some reason. Ifyou cannot find a copy of ZZSQLCI2 on the $SYSTEM disk, use DSM/SCM to export the filefrom the software archive. (ZZSQLCI2 is a component file of the TSQLCI2 product, T9198.)For more information, see the SQL/MP Installation and Management Guide. For informationon exporting the file from the Archive, see NonStop Software Essentials online help.
Although NonStop SQL/MP requires that you initialize SQL before you start DSM/SCM, NonStopSQL/MX does not require this step. For information about installing NonStop SQL/MX, see theSQL/MX Release 3.2 Installation and Upgrade Guide.
98 Resuming Normal Operations
Cold Start the Pathway Configuration1. 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.2. Run the PATHCOLD macro from the ZDSMSCM subvolume to cold start the Pathway
configuration.
Start DSM/SCM1. From the ZDSMSCM subvolume, start DSM/SCM:
> RUN STARTSCM
Because the $ZHOME reliable home-term process is not an interactive process and is alwayspaused, no action is necessary.
2. Press Enter. STARTSCM automatically runs the IP6031 TACL macro. This step can take severalminutes.
Run merge_whatisAfter coldloading the system, run the OSS merge_whatis command. (ZPHIRNM notifies you ifyou need to run it.) (The merge_whatis command is a shell script in /bin that creates andupdates the whatis database used by the OSS shell man, apropos, and whatis commands.)You might have a shell script that runs either one or both of the following, depending on your OSSenvironment:
/bin/merge_whatis
NOTE: You can run the Pcleanup utility on any file that is managed and audited by DSM/SCMbefore running the merge_whatis command. However, the OSS utility, Pcleanup cleans up OSSfiles, but not DSM/SCM files, in the OSS file system. Only the DSM/SCM CLEANOSS macrocleans up DSM/SCM files in the OSS file system. The CLEANOSS macro is run only if you fallback and then migrate again to a new PVU. During a Build/Apply, DSM/SCM automaticallyprompts you to run the CLEANOSS macro.
1. Log on to OSS as the super ID (255,255):
Current volume is $SYSTEM.STARTUP$SYSTEM STARTUP 1> osh
2. Change directories by using the cd command. For example:
/G/SYSTEM/STARTUP: cd /usr/share/man
3. Run the merge_whatis command:
/usr/share/man: merge_whatis
4. Enter the list (ls) command:
/usr/share/man: ls
cat1 cat4 cat7 whatis.frag
cat2 cat5 cat8 whatis_old
cat3 cat6 whatis
Run merge_whatis 99
/usr/share/man:
After you run merge_whatis, the directory contains a file named whatis, containing thedatabase. If you have previously installed OSS, a file named whatis_old is present, containingthe previous version of the database.
Configure Specific Products (Post-System Load)This section contains information about the configuration of various products such as OSS andSMF. See product-specific documentation for more information on installation and configuration.
Update NonStop TCP/IP Configuration Files
NOTE: You must have all the NonStop TCP/IP configuration files in your $SYSTEM.ZTCPIPsubvolume. Otherwise, applications dependent on proper network connections will fail.Alerts:
• See “Back Up (Copy) Files in the $SYSTEM.ZTCPIP Subvolume (Best Practice)” (page 84).
• Keep your current PROTOCOL file in your $SYSTEM.ZTCPIP subvolume. Update it (if necessary)with the new lines from the sample PROTOCOL file (SMPLPROT).
Step 1: Copy the Sample TCP/IP Files Into $SYSTEM.ZTCPIP (Optional)You need to copy the sample files if you do not have any of the following NonStop TCP/IPconfiguration files in your $SYSTEM.ZTCPIP subvolume:
• HOSTS
• PROTOCOL
• NETWORKS
• PORTCONF
• RESCONF
• SERVICESPerform a FUP DUP operation to rename the sample configuration files from this RVU SUT to thereal file name.
NOTE: Copy these configuration files only if you do not already have versions of these files.Depending on your applications, if you copy the configuration files, you might have to insertprevious network port information into each individually copied file.
The sample configuration files are named:
• SMPLHOST
• SMPLPROT
• SMPLNETW
• SMPLPORT
• SMPLRESC
• SMPLSERVTo copy the sample files:
>FUP DUP $SYSTEM.ZTCPIP.SMPLHOST, $SYSTEM.ZTCPIP.HOSTS>FUP DUP $SYSTEM.ZTCPIP.SMPLPROT, $SYSTEM.ZTCPIP.PROTOCOL>FUP DUP $SYSTEM.ZTCPIP.SMPLNETW, $SYSTEM.ZTCPIP.NETWORKS
100 Resuming Normal Operations
>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 makesure that the PROTOCOL file contains ipv6 and icmpv6 entries. If these entries are absent, a networkfailure might occur because the new socket routines present in TELSERV, LISTNER, and FTP accessthe entries in the PROTOCOL file.
If the PROTOCOL configuration file exists in $SYSTEM.ZTCPIP, you must add two lines from thesample PROTOCOL file (SMPLPROT). Find the lines in SMPLPROT from the SUT that refer to IPV6and ICMPV6 and copy those lines into your $SYSTEM.ZTCPIP.PROTOCOL file. For example:
12> TYPE SMPLPROT## @(#)protocols 1.1 Tandem## Internet (IP) protocols# This file is never consulted when the yellow pages are running#ip 0 IP # internet protocol, pseudo protocol numbericmp 1 ICMP internet control message protocolggp 3 GGP gateway-gateway protocoltcp 6 TCP transmission control protocolpup 12 PUP PARC universal packet protocoludp 17 UDP user datagram protocolipv6 41 IP internet protocol for v6icmpv6 58 ICMP internet control message protocol for v6
Step 3: Optional: For Planner Interface, Ensure That PORTCONF and SERVICES Files Are CompleteThe PORTCONF file specifies the ports that the LISTNER process listens to and the correspondingserver program it invokes when the request comes in.If you copied files as documented in Step 1, for the DSM/SCM Planner Interface to work, you mustadd a services line corresponding to DSM/SCM in the PORTCONF file (shown in bold lettering)and save the file. If you did not copy the files as documented in Step 1, no action is necessary.An example of the PORTCONF file:
58> type portconf## This file tells the listner program which ports to# listen to, and what programs to run# Telnet is directly, and does not use the listner's# services.# To run the listner use:# $system.ztcpip.listner / name.../ [config-file-name]# where config-file-name is this file.#
ftp $system.ztcpip.ftpservfinger $system.ztcpip.fingserv7 $system.ztcpip.echoservphiwsock $dsmscm.zdsmscm.pdpexe
Applications use the SERVICES file to retrieve the service port numbers and service names. If youcopied files as documented in Step 1, check that the last lines of the SERVICES file have an entrysimilar to:
Configure Specific Products (Post-System Load) 101
phiwsock 1089/tcp #DSM/SCM Planner Interface
For DSM/SCM, the port number is user-definable. The setup default is 1089. In the ZDSMSCMsubvolume, check the INITSTAT file for the recently configured TCP/IP port number. INITSTAT iscreated by DSM/SCM when INITENV is run.
Configure OSSSee the Open System Services Management and Operations Guide and the Open System ServicesInstallation Guide for information about updating and maintaining OSS database files.See the Open System Services Management and Operations Guide and the Open System ServicesInstallation Guide for information about updating and maintaining OSS database files. See theIUG2 for new OSS features and for a summary of migration or installation issues.
Install Specific OSS Files Using COPYOSS or PINSTALLFor those products that are not managed by DSM/SCM, you must install them using COPYOSSor PINSTALL or both.
• If any OSS files are managed by DSM/SCM, use PINSTALL on the remaining pax archives.See the OSS Management and Operations Guide for a description of PINSTALL use or thepinstall(1) reference page in the OSS Shell and Utilities Reference Manual.
• If no OSS files are managed by DSM/SCM, use COPYOSS for all of the OSS pax archivesin the ZOSSUTL subvolume. See the OSS Management and Operations Guide for a descriptionof COPYOSS use or the copyoss(8) reference page in the OSS Shell and Utilities ReferenceManual. Then use PINSTALL to install any pax archives in other subvolumes. See the OSSManagement and Operations Guide for a description of PINSTALL use, or the pinstall(1)reference page in the OSS Shell and Utilities Reference Manual.
NOTE: Features introduced in J06.12 affect the default security settings for OSS. These changesimpact where you install OSS packages onto your system. See Support Note S12018 for detailedinformation.
See also the appropriate product’s softdoc for any pre- or post-installation instructions.
Run the inetd ProcessRun the inetd process immediately after loading the OSS product files into the OSS environment.The inetd process listens for connections on certain Internet sockets. When a connection is foundon one of its sockets, inetd determines what service the socket corresponds to and invokes aprogram to service the request.For those products that are not managed by DSM/SCM, you must install them using COPYOSSor PINSTALL. See the appropriate product’s softdoc and installation instructions.
NOTE: To preserve the original inetd.conf file—before using COPYOSS or PINSTALL—thefollowing steps must be done to prevent COPYOSS or PINSTALL from overwriting the originalinetd.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.conf
102 Resuming Normal Operations
Using OSS Unautomated Configuration and StartupUnautomated configuration and startup is described in Appendix B in the Open System ServicesManagement and Operations Guide.
Using OSS EasySetup (T0585)The OSS EasySetup product (T0585) is available for automated setup, as described in the OpenSystem Services Installation Guide. OSS EasySetup is a series of TACL scripts that assist a sitewhen configuring and installing a minimal OSS subsystem for the first time or when starting,stopping, or removing an OSS subsystem.
Configure SMF (Optional)If you plan to configure SMF, an optional product, note:
• Migration of data from direct volumes to SMF logical volumes is documented in the StorageManagement Foundation User's Guide.
• Performance-critical applications that optimize the physical location of their data might needto specify the PHYSVOL option when creating data files, instead of relying on the SMFfile-placement algorithm.
• NonStop SQL/MP 3.x must be up and running before you start SMF.
CAUTION: To maintain data integrity, do not place these items on a virtual disk process(VDP):
◦ SWAP files
◦ TMF audit data
◦ DSM/SCM files
To ensure system configuration integrity, always:1. Save the system configuration after SMF configuration changes are made.2. Reload the system from the current system configuration file or the latest version with SMF
changes.See the softdoc T8472ACK or later for SMF configuration and interoperability considerations.
Configure the Remote Database FacilityThe AUDITTRAILBUFFER parameter is a modifier to DP2, which improves the performance of RDF.Ensure that an appropriate value is specified for the AUDITTRAILBUFFER modifier for the masteraudit-trail disk process. The AUDITTRAILBUFFER parameter allows you to specify how manymegabytes of buffer space to allocate for the audit-trail buffers.See the SCF Reference Manual for the Storage Subsystem for information on configuring the buffersize and check the DP2 softdoc for more information for J06.10 and later RVUs.
Configure the WAN ManagerIf you have a SWAN or SWAN 2 concentrator:1. Configure the WAN manager as described in the WAN Subsystem Configuration and
Management Manual.2. Update the SWAN CLIP firmware. See either the SWAN Concentrator Installation and Support
Guide or the SWAN 2 Concentrator Installation and Support Guide.
Configure Specific Products (Post-System Load) 103
Set Up iTP WebserverIf iTP WebServer was installed and was being used with the previous RVU, the same iTP Webserverinstallation would not work after the RVU upgrade. To get the iTP WebServer installation working(both T8996 and T8997) after an RVU upgrade, you must re-configure and set up iTP WebServerat the same OSS location using the setup script.
Re-deploy NonStop SOAP 4If NonStop SOAP 4 was deployed and was being used with the previous RVU, the same SOAP 4installation 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 NonStopSOAP 4 deployment directory, using the NonStop SOAP 4 deploy script.
104 Resuming Normal Operations
11 Backing Out the DSM/SCM RevisionProducts That Might Have Fallback Implications
Review the J06.nn Release Version Update Compendium for this RVU and product softdocs tomake sure that your installed products do not have migration implications.
Open System ServicesBack up the OSS configuration database files before falling back. For more information, see theOpen System Services Management and Operations Guide.
Storage Management FoundationThe record format of the system configuration database sometimes changes between RVUs and isautomatically converted to the new format the first time the system is loaded. To ensure systemconfiguration integrity, always:1. Save the system configuration after SMF configuration changes are made.2. Reload the system from the current system configuration file or the latest version with SMF
changes.
CAUTION: Create a saved version of the configuration before loading a new RVU or revision.If this step is omitted, you cannot fall back to a previous RVU or revision.
For more information, see the Storage Management Foundation User’s Guide and the requiredSMF softdocs.
Before Backing Out the Revision1. Confirm that the spooler is active and not 100 percent full.
a. At a TACL prompt, start SPOOLCOM and issue a COLLECT, STATUS command. Forexample:
12> spoolcom $spls; collect, status
COLLECT STATE FLAGS CPU PRI UNIT DATA FILE %FULL
$S ACTIVE 3 , 1 154 4 $OPS0.SPL.DATA 4
If the spooler is not active, start the spooler.
You will use the spooler to print out operator instructions when backing out the revision.
2. Start the TMF subsystem and DSM/SCM if they are not already running. For example:
4> TMFCOM START TMF5> volume $dsmscm_vol.ZDSMSCM6> RUN STARTSCM
where $dsmscm_vol is the DSM/SCM volume.
Start the Target Interface (ZPHITI)1. From the DSM/SCM subvolume, enter:
RUN ZPHITI
The TI Logon screen appears:
DSM Software Configuration Manager TI Logon
Products That Might Have Fallback Implications 105
==============================================================================
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. 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. T6031H01 11NOV2004
(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 and password and press F1 to log on to the Target Interface.The Main Menu appears:
DSM Software Configuration Manager Main Menu ============================================================================== \ELI Prior snapshot 2007-04-14:18:03:03
Selection number: 0
============================================================================== Choose an action by entering the selection number of an item from the list below. ============================================================================== 1 Create system report 2 Create system snapshot 3 Perform target activities 4 Perform audit 5 Perform database verify
9 Enable trace (for support use only)
============================================================================== F1-Select F4-Show Messages F15-Help F16-Return SF16-Exit Ready
Submit a Backout Request1. From the ZPHITI Main Menu, enter 3 (Perform target activities) in the Selection number field,
and press F1.The Target Menu - Select Target screen appears:
DSM Software Configuration Manager Target Menu - Select Target ============================================================================== \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
106 Backing Out the DSM/SCM Revision
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 youwant to back out of (selection 2 in this example), and press F1.The Target Menu - Select Action screen appears:
DSM Software Configuration Manager Target Menu - Select Action ============================================================================== \ELI Prior snapshot 2007-04-14:18:03:03 DEFAULT Last S/W applied on SYS 00 on 2006-04-14:18:01
Selection number:
============================================================================== Choose an action by entering the selection number of an item from the list below. ============================================================================== 1 Perform/Review apply request 2 Perform backout to S/W Applied on SYS 03 on 2008-04-14:15:41 3 Review operator instructions for the last apply completed.
============================================================================== F1-Select F15-Help F16-Return SF16-Exit Ready
3. In the Selection number field, enter 2 (Perform backout to S/W), and press F1.The Backout - Verify Request screen appears, which shows:
• The SYSnn, date, and timestamp of the current software revision and of the previousrevision, which becomes the current revision when the backout request finishes
• The location where DSM/SCM will place the snapshot
• A warning that the request makes the last software applied on this target inaccessible
DSM Software Configuration Manager Backout - Verify Request ============================================================================== \ELI Prior snapshot 2007-04-14:18:03:03 DEFAULT Last S/W applied on SYS 00 on 2006-04-14:18:01
Snapshot location: \ELI.$SPR09
============================================================================== ATTENTION - This request is not reversible. Once the current configuration for this target is backed out, it cannot be made current again. ==============================================================================
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
Submit a Backout Request 107
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 Backoutscreen, which gives a description of the request, its processing status, and the location of theprevious SYSnn software affected by the request. The screen is updated with current statusinformation approximately every 15 seconds, as in these examples:
DSM Software Configuration Manager Backout - Processing Backout ============================================================================== \ELI Prior snapshot 2007-04-14:18:03:03 DEFAULT Last S/W applied on SYS00 on 2006-04-14:18:01 Backout 2000-04-18:10:59:34
============================================================================== Request is being processed. Status information will appear below indicating progress. ==============================================================================
Backout Awaiting start. 2000-04-18:10:59:34
============================================================================== F3-Restart F4-Show messages F6-Cancel request F15-Help F16-Return SF16-Exit
DSM Software Configuration Manager Backout - Processing Backout ============================================================================== \ELI Prior snapshot 2007-04-14:18:03:03 DEFAULT Last S/W applied on SYS00 on 2007-04-14:18:01 Backout 2006-04-18:11:00:39
============================================================================== Request is being processed. Status information will appear below indicating progress. ==============================================================================
Backout Processing. 2000-04-18:11:00:39
============================================================================== F3-Restart F4-Show messages F6-Cancel request F15-Help F16-Return SF16-Exit
After the software backout is finished, the Backout - Complete Backout screen appears withoperator instructions.A complete set of operator instructions might look like this:
DSM Software Configuration Manager Backout - Complete Backout ============================================================================== \ELI Prior snapshot 2007-04-14:18:03:03 DEFAULT Last S/W applied on SYS on 2006-04-14:18:01
Print operator instructions on: ============================================================================== 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. Refer to the release documentation for detailed information on migrating to this software configuration.
108 Backing Out the DSM/SCM Revision
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 SYS004. 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.
============================================================================== F4-Show Messages F9-Print operator instructions F15-Help F16-Return SF16-Exit Task completed successfully.
5. Enter a printer location and press F9 to print the operator instructions. You might need tomodify these instructions before returning to the previous RVU. For instance, you might notneed to change the firmware unless you have to replace hardware that can be supported onlyby the new RVU.
6. Press SF16 to exit the Target Interface.
Monitor the Backout Process Using NonStop Software Essentials1. Log on to NonStop Software Essentials.2. Select Requests->Show requests.
The Requests status page appears, showing the type and status of various DSM/SCM requests.3. From the Request list page, click your backout request name.
The Request Status page displays detailed information about your backout request.This example indicates that the backout request finished successfully:
Monitor the Backout Process Using NonStop Software Essentials 109
Monitor the Backout Process Using the Planner Interface1. Log on to DSM/SCM (Start+Programs+dsm_scm→dsmscm).2. 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.This example indicates that the backout request finished successfully:
110 Backing Out the DSM/SCM Revision
12 Running ZPHIRNM to Reactivate the Previous SoftwareRevision
This step runs the ZPHIRNM program again to change the temporary names of the previous productfiles back to their actual names.
Fallback Considerations for NonStop Software Essentials After ZPHIRNMIf after migrating to this RVU, you decide to fall back to an RVU earlier than J06.13 or H06.24,you need to be aware of the fallback considerations for NonStop Software Essentials. NonStopSoftware Essentials 2.0 components are not compatible with NonStop Software Essentials 1.0components.When you fall back, the ZPHIRNM step may rename the files in $SYSTEM.ZNSE, and you mightnot be able to continue using NonStop Software Essentials after reloading the system. These arethe possible fallback scenarios you might encounter:• If the T0894 H02 server was already installed on the fallback RVU, there should be no
problems.• If the T0894 H01 server was installed on the fallback RVU, you can either revert to using the
T0895 V01 client from another CMS, or preferably you can install the T0894 H02 server asdescribed in the Nonstop Software Essentials Installation and Quick Start Guide.
• If no version of NonStop Software Essentials was installed on the fallback RVU, you can eitherrevert to using the DSM/SCM Planner Interface, or you can install the T0894 H02 servermanually as described in the Nonstop Software Essentials Installation and Quick Start Guide.
AlertsBefore running ZPHIRNM:
• Applications that use files that are being replaced should not be running. To avoid anypossibility of conflict, stop all applications, except for the TMF subsystem, before runningZPHIRNM.
• You must have rename (purge) access to all files being renamed. You can ensure this accessby running ZPHIRNM as the super ID (255,255).
• If you are connected to an Expand network, you might see a message stating that the NonStopSQL file, ZZSQLCI2, was not renamed during ZPHIRNM. However, on further examinationof the log file, you may find that ZPHIRNM did finally rename the file, in which case you canignore the error message and continue.
• Make sure that you drain the spooler before running ZPHIRNM. If you drain the spooler afterrunning ZPHIRNM, an error message appears indicating that the spooler program and libraryversions are different, and spooler terminates with errors.
Drain the Spooler (Optional)Before executing the SPOOLCOM;SPOOLER,DRAIN command:
• Use the SPOOLCOM;COLLECT $collector-process, LISTOPENS command to identifyprocesses that currently have jobs open.
• Use the SPOOLCOM;JOB (STATE PRINT) command to determine which jobs are currentlyprinting.
Fallback Considerations for NonStop Software Essentials After ZPHIRNM 111
• Take the appropriate action to ensure that these jobs either terminate when finished or arestopped.
• Drain the spooler. To drain the spooler, log on as a super group user (255,n), accessSPOOLCOM, and enter the following command:
SPOOLCOM> SPOOLER, DRAIN
This command causes the spooler to move from the active to the dormant state.
CAUTION: Do not use the TACL STOP command to drain or stop the spooler. Also, do notissue the TACL STOP command after you have issued the SPOOLCOM DRAIN command. Thecontrol file can be corrupted during the next warmstart or rebuild.
For more information on draining the spooler and recovery, see Chapter 1 in the SpoolerUtilities Reference Manual.
Run ZPHIRNM
Using PREVIEW ModeYou can do a preview run of ZPHIRNM to check that the target subvolumes (TSVs) and associatedmap files are consistent. Running ZPHIRNM in PREVIEW mode simulates the ZPHIRNM processwithout actually updating files or activating the configuration. In PREVIEW mode, ZPHIRNM indicateswhether or not TMF needs to be up when running ZPHIRNM.
Run ZPHIRNM1. 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. When asked if you want to use a log file with the session, type Y and press Enter.3. When prompted, type a file name for the log file, and press Enter.4. ZPHIRNM issues this message and begins processing:
Log file, <filename>, was successfully created.
5. Verify that ZPHIRNM ran successfully.
112 Running ZPHIRNM to Reactivate the Previous Software Revision
6. Review the log file.7. If ZPHIRNM did not run successfully, correct the problem and rerun.
Two types of error and warning messages are issued during the renaming process:
• If a fatal error occurs, ZPHIRNM immediately issues an error message and stops.
• A nonfatal error is one that affects processing only for a single subvolume. If a nonfatalerror occurs, ZPHIRNM issues an error message and attempts to restore the subvolumeit is currently processing to its original state.
◦ If the subvolume is successfully restored, ZPHIRNM continues with the next subvolume.
◦ If the subvolume cannot be restored, ZPHIRNM issues an additional error messageand continues with the next subvolume.
◦ If the subvolume was successfully processed, you can ignore warning messages.See the NonStop Software Essentials User’s Guide for troubleshooting proceduresand the DSM/SCM Messages Manual for a complete list of ZPHIRNM messages.
Run ZPHIRNM 113
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 thischapter that describe CLIM fallback procedures.
Fallback Considerations for the Power RegulatorThe OSM Service Connection does not support the Power Regulator feature in RVUs prior to J06.14;therefore, falling back to an RVU prior to J06.14 always results in all server blades running in thedefault Status High Performance Mode.
AlertsBefore performing a system load:
• Before halting the processors, stop running applications, including TMF.
NOTE: To stop TMF, at a TACL prompt, enter: TMFCOM STOP TMF
• Do not close the System Startup dialog box while startup is in progress. If you attempt to closethe dialog box, a message dialog box appears to alert you that the system startup processwill be stopped if you continue.
• If you stop a system startup before it has finished, the state of your system will be unpredictable.You might need to perform another system startup to enable the system to resume normaloperation.
• If you must stop the system startup process, click Abort. (The abort process should take effectwithin 30 seconds.)
• For detailed information on performing a system load, see the NonStop Operations Guide.
• List your saved configuration files by entering:
FUP INFO $SYSTEM.ZSYSCONF.CONF*
You might want to refer to this list later in the procedure.
• If you are falling back and using next generation CLIMs and SAS disk enclosures, the systemto which you are falling back needs SPRs to support those components. See the CLuster I/OModule (CLIM) Software Compatibility Reference for this information.
• Check the list of fallback issues in the J06.nn Release Version Update Compendium, whereJ06.nn is the RVU to which you are falling back.
Task OverviewIf you have CLIMs in your system and need to fall back to the previous version of the CLIM software,the steps to fall back on the CLIM are included in these procedures. If reverting to the previousCLIM software is necessary or desirable, the CLIM must be reimaged, as described in theseprocedures. Refer to the CLuster I/O Module (CLIM) Software Compatiblity Reference to determinewhether reverting to the previous CLIM software is necessary for your fall back scenario. If yoursystems does not have CLIMs installed, you can disregard these steps.
114 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations
Restoring the CLIMs assumes that you have saved the CLIM configurations by issuing the CLIMBKUPcommand before upgrading your system, as described in “Back Up CLIM Configuration Files”(page 44) and in the Cluster I/O Protocols (CIP) Configuration and Management Manual. Fallingback to previous versions of CLIM software adds approximately one hour for each CLIM to theprocess of loading the system on the previous RVU.
NOTE: When you fall back, you must restore CLIM configuration files saved from the same RVUas the NonStop system RVU to which you are falling back.
The procedure for falling back on the CLIM and loading the NonStop system on the previous RVUis:1. Before halting the processors:
a. Collect information about the CLIM environment.b. Modify the OSSINFIL file.
2. Halt the processors.3. While the processors are halted:
• Revert the server blade firmware, hard reset the system, and reimage the CLIMs.
• Prepare the CLIMs. Preparing the CLIMs involves configuring the interfaces that are usedfor the dedicated service LAN and for the Maintenance Providers, configuring the StorageCLIM for its role in the system, and configuring all the CLIMs with the system informationyou gathered before halting the system.
4. Load the system.5. Once the system is loaded, complete the CLIM setup. This step involves running a script that
establishes a secure relationship between the CLIMs and the system. In addition, you restoremore of the CLIM configurations by running a script that restores various aspects of the CLIMconfiguration from the stored file.
6. Revert firmware if necessary.7. Install specific OSS files if necessary.8. Verify that the system is started.
Before Halting the Processors
(Optional) Prepare to Fall Back to Previous CLIM FirmwareIf you will be falling back to previous CLIM firmware using the down system method, perform thePrepare for Down System CLIM Firmware Update action in the OSM Service Connection. For moreinformation, see the Cluster I/O Protocols (CIP) Configuration and Management Manual.
Prepare to Fall Back to Previous CLIM Software
NOTE: If the system disk is a SAS disk, the SAS disk enclosures that contain the system disks(both primary and mirror) must have LUNs assigned prior to a reimage and must not be power-cycledduring the reimage process.
Following are preparatory steps for downgrading to a previous version of the CLIM software.1. Obtain the password for the root user ID on the CLIM.2. Obtain a password for the super.super TACL user ID.3. Obtain the DNS name of each CLIM iLO. The default name is system-climname-ILO, for example,
mysys-n1002583–ILO.4. If you determined that reverting to the previous CLIM software is necessary, ensure you have
the CLIM software image for the RVU you are falling back to on either the NonStop systemconsole or a CLIM DVD. If you do not have the correct software image on a system console,
Before Halting the Processors 115
install it from the CLIM DVD by following the procedure in the CLuster IO Protocols (CLIM)Configuration and Management Manual.
5. 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 CLIMBoot Service Configuration Wizard or the NonStop Maintenance LAN DHCP DNS ConfigurationWizard, depending on which one you have installed on your NonStop system console.Instructions for the CLIM Boot Service Configuration WizardWhichever wizard you have is launched from the Windows Start menu by selecting AllPrograms > HP OSM, followed by the name of the wizard. Instructions for using the CLIM BootService Configuration Wizard begin at b.
NOTE: If you have the NonStop Maintenance LAN DHCP DNS ConfigurationWizard installedon your system consoles—it must be installed on both consoles on the dedicated serviceLAN—see the NonStop System Console Installer Guide for instructions on configuring thatwizard for first-time use on your LAN. Then use the online help available from within the wizardto determine if one or more CLIMs you are downgrading is being used for BOOTP and DHCPservices.
a. Determine the IP address of the CLIM(s) you are going to downgrade. Use the OSMService Connection to identify the Maintenance Interface IP Address for the CLIM.
b. To launch the CLIM Boot Service Configuration Wizard from a NonStop system console,go to the Windows Start menu and select All Programs > HP OSM > CLIM Boot ServiceConfiguration Wizard and launch the wizard.The initial dialog box asks whether you want to "Configure Boot Service on CLIM(s)" or"Disable existing Boot Service on CLIM(s)" and whether or not there is a "peer NSCinstalled."
116 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations
c. Select Configure Boot Service on CLIM(s) and the appropriate option for whether or notthere is a peer NonStop console installed. (If there is a peer, you are then prompted forthe credentials of that peer console.)The next dialog box shows the IP addresses for the one or two CLIMs configured asBOOTP/DHCP servers.
d. 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.
Before Halting the Processors 117
6. Obtain the system name, netmask, gateway, and IP address for the CLIMs. If this informationis unavailable from your environmental documentation, continue with the next step to obtainit directly from your system. Otherwise, skip the next step.
7. 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.N1002583, DETAIL
The NonStop host system name in this example is \BLJCQA2 and the maintenanceinterface IP address is 192.168.37.83.
b. Use the climcmd clim-name climconfig interface -info eth0 commandfrom a TACL prompt for the CLIMs to obtain the netmask and gateway. For example:>climcmd N1002583 climconfig interface -info eth0
comForte SSH client version T9999J06_07Jul2008_comForte_SSH_0080Interface : eth0Interface Type : Physical InterfaceJumbo Frame : NOIP Address : 192.168.37.83 Netmask : 255.255.0.0
In this example, the netmask is 255.255.0.0 and there is no gateway configured.c. Use OSM Low-Level Link to connect to the CLIM and obtain PCI Slot configuration
information.d. Make note of all values.
When Falling Back to the J06.04 or Earlier RVU
Modify OSSINFILWhen falling back to the J06.04 or earlier RVU, then before halting the processors, you mustrestore the SERVER #ZPLS entry in the OSS subsystem maintenance file OSSINFIL on all systemswith OSS installed. If you commented out this entry when installing this RVU, use TEDIT to modifythe entry as follows:TEDIT $SYSTEM.ZOSSINS.OSSINFIL
Then change* SERVER #ZPLS
toSERVER #ZPLS
This change is required for correct startup of OSS.
If Using CLIMs for BOOTP, DHCP, or DNS ServicesWhen falling back to the J06.04 RVU, if the CLIM or CLIMs you are downgrading are being usedfor BOOTP, DHCP, or DNS services instead of the system consoles on your LAN, you must migratethese services to the NonStop System Console. See the service procedure: Changing the DHCP,DNS, or BOOTP Server From CLIMs to System Consoles.
Halt the Processors1. Log on to the OSM Low-Level Link.2. On the toolbar, click Processor Status to display the Processor Status dialog box.3. In the Processor Status box, select all processors.4. From the Processor Actions list, select Halt.5. Click Perform action.
118 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations
6. Click OK when asked “Are you sure you want to do Halts?”7. When the Action Status box confirms that all processors have halted, close the Processor Status
dialog box.
While the Processors are HaltedIf necessary, revert the Server Blade firmware (HSS, DISKBOOT, and ISP1040), then hard resetall processor blades as follows:
NOTE: If this is a NonStop Blade System, NS200 series, or NS2100 system and the DHCP,DNS, and BOOTP services for your dedicated service LAN are hosted on CLIMs that you willreimage as part of this fall back, see “Prepare the CLIMs” (page 130) for instructions on copyingthe appropriate HSS files (this operation also copies DISKBOOT and ISP1040 files) for all applicablesystems after you reimage the CLIM and before loading the system.
NOTE: Firmware is backward compatible. HP recommends that you retain current firmware, andrevert to previous firmware only when necessary.
1. Log on to the OSM Low-Level Link.2. On the toolbar, click Processor Status to display the Processor Status dialog box.3. Under Processor Status, select all processors.4. From the Processor Actions list, select Hard Reset.5. Click Perform action.6. Click OK when asked “Do you really want to perform a Hard Reset on the selected
processor(s)?”7. When the Action Status box confirms that all processors have been reset, close the Processor
Status dialog box.
(Optional) Fall Back to Previous CLIM FirmwareIf you are falling back to previous CLIM firmware using the down system method, use the DownSystem CLIM Firmware Update Tool. For more information, see the Cluster I/O Protocols (CIP)Configuration and Management Manual and the online help available from within the tool.
Reimage the CLIMsThis procedure is necessary only if you are reverting to the previous CLIM software.
NOTE: Only reimage the CLIMs if you need to revert their software to an older version. Checkthe CLuster I/O Module (CLIM) Software Compatibility Reference to determine which versions ofthe CLIM are compatible with the target RVU.
NOTE: To downgrade to CLIM DVD version T0853AAH, you must first downgrade the iLOfirmware to 1.77. Using the OSM Service Connection, right click the CLIM, select Actions, selectiLO Update, and specify the file location for iLO firmware 1.77. Repeat this process for each CLIM.
1. Using a browser, log onto the iLO using the CLIM DNS name or CLIM iLO IP address, usernameand password. For example, enter this string in the URL of the browser, substituting the realDNS name or IP address for the variable:https://dns-name or IP-address
You will receive a security alert:
NOTE: The security alert for CLIM configured with Internet Explorer 7 looks slightly differentfrom what is shown in this example.
While the Processors are Halted 119
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.
120 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations
4. Only do this step if you receive the error: With Internet Explorer 7, you must enable the Javaapplet to use the Virtual Media.a. Go to the control panel, select Java, then select the advanced tab:
1 Control panel2 Java3 Control panel dialog box for Java, Advanced tab
b. Expand <APPLET> tag support, and check Internet Explorer.
While the Processors are Halted 121
5. This screen pops up, along with a warning. Click on the JavaScript screen to activate it, thenclick Yes in the warning box.
6. This is the default iLO 2 Virtual Media window:
122 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations
a. In the Virtual CD/DVD-ROM area of the dialog box (1 in the following figure), select theimage 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 aCLIM Software DVD onto the console by following the procedures in the Cluster I/OProtocols (CIP) Configuration and Management Manual.
1 Use this area (Virtual CD/DVD-ROM) of the applet screen.2 This is where you specify the local image file.3 This is where you click Connect.
b. Click Connect beside the Local Media Drive field (3 in the above figure). The DVD imageis enclosed with the Green Box, similar to this screen:
While the Processors are Halted 123
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 theCLIM. On the pop up, click Yes.
124 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations
1 Power management tab.2 Momentary press tab.3 Warning pop up.
When the CLIM is shut off, the status shows Server is currently in STANDBY (OFF):
9. Push Momentary Press again to restart the CLIM. The status now shows that the CLIM is on.
While the Processors are Halted 125
10. Return to the console window.11. When the Debian splash screen appears, click within its window to activate it, and press
Enter. For G5 CLIMs, pressing Enter boots the CLIM:
For G6 CLIMs, only use the Install option:
126 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations
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.
While the Processors are Halted 127
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. (ClickingContinue has no effect; you must press Enter.)
128 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations
A status window appears:
After a brief pause during which the ProLiant window appears, a screen showing a successfulinstallation like this appears:
While the Processors are Halted 129
Prepare the CLIMsThis 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 maintenanceinterface usernames and passwords:• root/hpnonstop
• user/climb. At the Linux prompt, add the interface by entering this command:
climconfig interface –add eth0
c. Add the IP address and bring up the eth0 interface by entering:climconfig ip –add eth0 –ipaddress ip-address -netmask netmask
2. Reboot the CLIMs by entering:reboot
3. Use OSM Low-Level Link to perform the Configure action on each CLIM. In the Configure CLIMdialog box, enter all the information that you gathered before starting this procedure. (Inpre-ABK versions of OSM Low-Level Link, the PCI Slot Configuration area shows thepossible PCI slot configurations in multiple drop-down menus. (This area is disabled for StorageCLIMs.))Sample Pre-ABK Version of OSM Low-Level Link, IP CLIM
In ABK and later versions of OSM Low-Level Link, the PCI Slot Configuration area hasthe 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
130 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations
The PCI Slot Configuration area is disabled for Storage CLIMs in pre-ABK, ABK andpost ABK versions of OSM Low-Level Link.Sample ABK or Later Versions of OSM Low-Level Link, Storage CLIM
Be sure to select the CLIM type for the type of CLIM you are configuring from the Mode ofoperation pull-down menu. After entering the required information in the dialog box, pressConfigure. Here is an example screen showing the CLIM preparation has successfullycompleted:Sample Pre-ABK Version of OSM Low-Level Link, IP CLIM
Prepare the CLIMs 131
Sample ABK or later Version of OSM Low-Level Link Version, IP CLIM
4. Click Yes. The CLIM reboots.5. 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 thatconnect to the system disks:lunmgr ––approve yesall
132 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations
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:0interface. Using the IP address and netmask of ZTCP0 and ZTCP1 you collected by using theSCF INFO CLIM DETAIL and CLIMCMD interface -info commands prior to starting thedowngrade, and using the iLO serial console, enter these commands at the Linux prompt:climconfig interface -add eth0:0
climconfig ip -add eth0:0 -ipaddress 192.168.36.10 -netmask 255.255.0.0
7. If you reimaged both CLIMs and they were being used to host DHCP, DNS, and BOOTPservices on your dedicated service LAN, as determined in “Prepare to Fall Back to PreviousCLIM Software” (page 115), and this is a J-series system that relies on these CLIMs to provideBOOTP servers (i.e., all NonStop systems running J-series software except for NS2000), youmust log on to the OSM Low-Level Link and copy the system-specific HSS file to the CLIMsnow—before loading the system—as described in “Complete CLIM Setup” (page 135). If thissystem does not need CLIM-based BOOTP services but other systems on your LAN do, youcan perform this OSM Low-Level Link logon and copy HSS file procedure later.
Load the SystemA normal system load consists of loading the operating system from disk into the memory ofprocessor 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. In the SYSnn field, enter nn, which is the number of the system subvolume that containsthe version of the operating system you will load.
b. 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. Fora description of the CIIN file, see the appropriate planning guide for your system.
3. Under Configuration File, select Saved Version (CONFigxx.yy:).Refer to the list of configuration files generated before beginning this procedure.
4. Under Configuration, ensure that the correct paths are checked.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 mightwait up to 30 seconds before the abort takes effect.
CAUTION: Do not close the System Load dialog box while startup is in progress. If youattempt to close the dialog box, an OSM message box indicates that the system startup processwill be stopped if you continue. If you stop a system startup before the operation finishes, thestate of your system cannot be predicted. You might need to perform another system startupto enable the system to resume normal operation.
If one or more of the startup event stream windows or startup TACL windows does not launchon the system console after a few minutes (5 to 8 minutes), abort system startup, close theOSM Low-Level Link, reboot the system console, and restart the system load using the OSMLow-Level Link again.
6. Monitor the system startup process. Messages indicating the progress and completion of thesystem load, and the reload of processors indicated in the CIIN file, appear in these displaylocations on the system console.When the system load is complete (the operating system is loaded successfully into the memoryof processor 0 or processor 1), the Detailed box on the System Load dialog box displays:
Load the System 133
SYSTEM STARTUP COMPLETE, NSK RUNNING ON PROCESSOR n
• If the system load fails, check for the appearance of any halt codes or messages. Forrecovery procedures, see the Processor Halt Codes Manual or Operator Messages Manual.
• After the operating system is running on the server, messages are no longer sent to theDetails box. See the event messages sent to the startup event stream window.
Complete the System Load (If Necessary)Loading the processors with the CIIN file is usually automatic. However, if the operating systemloaded successfully into processor 0 or processor 1, but the commands in the CIIN file do notreload all remaining processors, use the following TACL RELOAD command. You must be superID (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:
TACL> RELOAD *, PRIME
2. To load an individual processor, enter:
TACL> RELOAD nn
where nn is the processor number of the processor you want to reload.If the reload is initiated successfully, this message appears in a startup TACL window on thesystem console screen:
PROCESSOR RELOAD: nn
Using the SSOCLIM * Option to Run SSOCLIM on All Available CLIMsFor this RVU, SSOCLIM can be made to run on all available CLIMs by using the * option insteadof the CLIM IP or CLIM name in the SSOCLIM command line:SSOCLIM [{CLIM NAME | IP | *}{CLIM USER} {PASSWORD}][FORCED]
Where:CLIM NAME
is the name of the CLIM to be used.IP
is the IP address of the CLIM to be used.*
runs SSOCLIM on all available CLIMs.CLIM USER
is the user name to be used against a CLIM when CLIM NAME or IP is used or against allavailable CLIMs when * is used.
PASSWORD
is the password to be used against a CLIM when CLIM NAME or IP is used or against allavailable CLIMs when * is used.
FORCED
, if specified, suppresses the warning instruction to run SSOCLIM on all the CLIMs.
134 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations
Complete CLIM Setup1. Establish trust between the CLIM and the NonStop host system.
If you are falling back to J06.09 (or to an RVU with T0682H02^ACC) or J06.10 (or to anRVU with T0682H02^ACI), you must run SSOCLIM as SUPER.SUPER. For all other RVUs, youcan run SSOCLIM as any SUPER group user. In both cases, you must run SSOCLIM twice,once with the root username and hpnonstop password, and once with the user usernameand clim password.a. At a TACL prompt, log on as SUPER.SUPER (for a fallback to J06.09 or J06.10) or as
any SUPER group user.b. Enter SSOCLIM.
The script prompts you for the CLIM name, IP address or DNS name of the CLIM. Enterthat parameter. Then the script prompts you for the username and password. Use theroot username and hpnonstop password.
c. Re-enter the SSOCLIM command using the user username and clim password.2. Use CLIMRSTR to restore all the CLIMs with the CLIM backup files from the previous CLIM
version. Restore the files that you stored when you followed the CLIM software upgradeprocedures in “Back Up CLIM Configuration Files” (page 44).
NOTE: The CLIM configuration files used during this procedure must be of the same RVU asthe RVU to which you are falling back.
For the J06.04 and J06.05 RVUs, rename and restore the backup files. For example, at theTACL prompt, enter:a. >FUP RENAME $DATA1.BCKJ0605.N1002583, $DATA1.BCKJ0605.BACKUPGZ
b. >CLIMRSTR N1002583 $DATA1.BCKJ0605
c. Repeat steps a. and b. for each CLIM.For J06.06 and later RVUs, restore the backup files. For example, at the TACL prompt, enter:a. >CLIMRSTR N1002583 $SYSTEM.N102583.BCKJ0606
b. Repeat for each CLIM.3. Reboot the CLIMs:
a. For large systems, boot one of every pair of CLIMs on the system at the same time.
NOTE: For IP CLIMs and Telco CLIMs you must know which CLIMs are configured asfailover pairs. For Storage CLIMS, you must know which pair of CLIMs are attached toa particular path or you will lose access to the disk.
b. Wait for all the CLIMs to be restored and wait for disk paths or IP addresses to returnbefore rebooting the next CLIM.For Storage CLIMs, use SCF status disk $*. For IP and Telco CLIMs, use CLIMCMDpsclim.>climcmd n1002583 psclim
If you do not see any running processes, use the CLIM command to clear the log andstart. For example (IP CLIM):>climcmd n1002583 clim clearlog; clim start
For Storage CLIMs, after clearlog, you must reboot again. For example (Storage CLIM):>climcmd s1002533 clim clearlog>climcmd s1002533 clim reboot-nodebug
Complete CLIM Setup 135
c. Reboot the other set of CLIMs, that is, the other CLIM in each failover pair or the otherCLIM in each pair that connects to a particular disk.
d. If the system disk is a SAS disk and you have SAS disk enclosures that contain the systemdisks (both primary and mirror), check the LUN manager status to be sure they arefunctional. For example:1) Check lunmgr status:
>climcmd clim-name lunmgr –p
2) If the above command did not display any LUN information, issue these commands:>CLIMCMD clim-name lunmgr -a yesall
SCF> allow all errorsSCF> reset disk $*SCF> start disk $* - Say Yes when it promptsSCF> status disk $*-*, sel not started
4. If you reimaged a CLIM being used for DHCP, DNS, and BOOTP services on your LAN, usethe OSM Low-Level Link from each system that relies on getting its HSS files as part of thisBOOTP service (i.e., all NonStop systems running J-series software except for NS2000) anduse the Copy HSS Files action to create and copy the system-specific HSS file to the CLIM.This action is available before and after system discovery.a. Before system discovery, click Copy HSS Files on the toolbar or select Copy HSS Files from
the Tools menu.
b. After system discovery, you must select Copy HSS Files from the Tools menu.
c. Selecting Copy HSS Files brings up the Update HSS dialog box. It displays the currentHSS version for each processor on the system
136 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations
d. Select the desired HSS version from the Available HSS versions drop-down menu.e. Enter the user name and password for every CLIM and the peer NSC to which the selected
HSS file needs to be copied and click Copy.5. If you reimaged a CLIM being used for BOOTP/DHCP/DNS services on your LAN, use the
OSM Low-Level Link to copy the HSS file to the CLIM. This action is available before and aftersystem discovery. Before system discovery, click Copy HSS Files on the toolbar or select CopyHSS Files from the Tools menu. After system discovery, select Copy HSS Files from the Toolsmenu.
6. If this is an IB CLIM, install third-party Informatica software for messaging and order sequencing.
Complete CLIM Setup 137
Revert Firmware (If Necessary)HP recommends running the latest firmware; however, if necessary, revert the following firmwareto the firmware on the SYSnnsubvolume from which you loaded the system:• FCSA firmware
• G4SA firmware
• ServerNet Adapter firmware
• ServerNet Clustering firmware
• Server Blade firmware (Requirements vary according to system type. See the documentationspecific to your NonStop system for details.)
• c7000 enclosure firmware, if applicable to your system (Onboard Administrator firmwareinstalled through FCO, if necessary)
• c7000 enclosure ServerNet Switch firmware (ME and ME FPGA), if applicable to your system
• IOAM ServerNet Switch firmware (ME and ME FPGA), if applicable to your system
• VIO enclosure firmware (ME and ME FPGA), if applicable to your system
• S-series interoperability firmware, if applicable to your system (Service Processor and ServiceProcessor B)
• SWAN/SWAN 2 Concentrator firmware
• SS7 Controller firmware, if applicable to your system
• CLIM firmware, if your system has CLIMs attached, and you did not update CLIM firmwarewhile the system was down
See the softdocs for details.
Install Specific OSS Files (If Necessary)For those products that are not managed by DSM/SCM, you must install them using COPYOSSor PINSTALL or both. For details, see “Install Specific OSS Files Using COPYOSS or PINSTALL”(page 102).
NOTE: Features introduced in J06.12 affect the default security settings for OSS. See SupportNote S12018 for detailed information.
Verify That the System Is StartedVerify that each processor is running the operating system:1. From the Summary menu in the OSM Low-Level Link, select Processor Status.2. The Processor Status dialog box should show each processor to be Executing NonStop OS.
138 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations
A Using DSM/SCM and NonStop Software Essentials toInstall SPRs
NOTE: Before performing the steps in this appendix install NonStop Software Essentials by usingthe 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. Thisappendix 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 NonStopServers, for example) that the SPR can be installed on that specific J-series RVU.
See the J06.nn Release Version Update Compendium for this RVU and the Interactive UpgradeGuide 2 (IUG2) for information on SPRs that you might need to apply to your current RVU beforeupgrading to this RVU and connecting to a G-series or H-series system.
Tools for Managing SPRsAlways keep an SPR log file that lists which SPRs have been reviewed, selected, and installed onyour system:• Update the SPR log regularly to maintain accurate and current information about the SPRs
installed on your system.• Document the reasons for a decision not to install SPRs that have been issued for products you
run on your system.
Scout for NonStop ServersUsing Scout for NonStop Servers, you can display detailed information about RVUs, SPRs, andprerequisites for SPRs. You can also access:• Outage Prevention Notifications (OPNs)• Hotstuff messages• Support Notes• RVU (softdocs) and softdoc addendumsAfter researching available SPRs, you can download those you consider appropriate for yoursystem directly to your workstation and then use FTP to transfer downloaded SPRs to your server,or you can request tape delivery.
DSM/SCMDSM/SCM has automatic features that can help you keep records of SPRs. You can use the NonStopSoftware Essentials to generate prepackaged reports, including reports that list:• The products on a system and the SPRs applied to those products• The SPRs that have been replaced by a specific SPR• The requisite SPRs for a selected SPRYou can also use the DSM/SCM Archive to export SPRs to different volumes.See the User’s Guide for more information.
Tools for Managing SPRs 139
SPRNOTESYou can use SPRNOTES to research an SPR before installing it. Read the installation instructionsand 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 remainingKeep a copy of each SPRNOTE and record the status of the related SPR. For example, recordwhether the SPR is not applicable, is already installed, or needs to be installed.
Install SPRs With DSM/SCMThe steps for using DSM/SCM to install SPRs are the same as those for installing a SUT.
Save the Current ConfigurationFirst, 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. At the SCF prompt, enter:
-> FUP INFO $SYSTEM.ZSYSCONF.CONF*
3. Save the current configuration by using a unique file name. At the SCF prompt, enter:
-> SAVE CONFIGURATION xx.yy
where xx.yy is a number from 0.0 through 99.99.
This example saves the current system configuration to the file $SYSTEM.ZSYSCONF.CONF1101:
-> SAVE CONFIGURATION 11.1The configuration file $SYSTEM.ZSYSCONF.CONF1101 has been created.
If you specify a configuration file that already exists, SCF asks you if you want to replace it. If youspecify that you do not want to replace the existing file, SCF does not overwrite the file. You mustenter another SAVE command to save the current configuration file.
Determine the Current SYSnnThere are several ways to record the current SYSnn subvolume on your system.You must use the current SYSnn subvolume if you need to fall back to your current RVU. You mustuse a different SYSnn subvolume to create a new software revision if NonStop Software Essentialsindicates that a SYSGEN is required.1. At a TACL prompt, enter:
$SYSTEM SUPER 6> sysinfo
SYSINFO - T9268H01 - (01 OCT 2004) SYSTEM \ELI Date 04 May 2007, 22:00:18COPYRIGHT 2003 Hewlett-Packard Development Company, L.P.
System name \ELI EXPAND node number 033 Current SYSnn SYS01
140 Using DSM/SCM and NonStop Software Essentials to Install SPRs
System number 000000 Software release ID J06.04.00
2. Issue a TACL FILEINFO command on $system.*.osimage to list the SYSnn subvolumes onyour system and determine which one is open.
$SYSTEM.SYS00 CODE EOF LAST MODIFIED OWNER RWEP PExt SExtOSIMAGE 0 57354240 15DEC2007 9:57 255,255 NUNU 200 200
$SYSTEM.SYS01 CODE EOF LAST MODIFIED OWNER RWEP PExt SExtOSIMAGE 0 57393152 05APR2008 8:56 255,255 NUNU 200 200
3. At a TACL prompt, enter a STATUS 0,0 command to see which SYSnn subvolume is currentlybeing used:
3> status 0,0
System \ELI
Process Pri PFR %WT Userid Program file Hometerm 0,0 201 P R 000 255,255 $SYSTEM.SYS01.NMONTOR $YMIOP.#CLCI Swap File Name: $SYSTEM.#0
Receive the SPR Into the DSM/SCM Archive
Before Starting DSM/SCMStart TMF if it is not already running:
> TMFCOM START TMF
Bring the SPR Into the DSM/SCM Archive1. Start DSM/SCM if it is not already running:
> volume $dsmscm_vol.ZDSMSCM> RUN STARTSCM
2. Start HP SIM and then open a NonStop Software Essentials window by selecting the ManageNonStop Software link on the NonStop server Tools & Links tab.
3. Click Receive software under the Software Installation group on the NonStop Software Essentialshome page.
4. Click the Input Source tab.5. If the SPR has been received on disk or has been restored from tape to disk, click inside the
Enter volume subvolume pattern input field.6. Enter the name of the distribution subvolume containing the SPR, and then click Find/Add.7. If the SPR was received on tape, click Tape and select a tape drive from the list.8. In the Receive Software Request dialog box, click the Scheduling tab.9. Enter the time you want your Receive Software Request to run. The default option is for the
request to run immediately. If this is what you want, click Submit.
Create a New Software Configuration That Includes the SPRAfter the SPR has been received into the Archive, you can copy it. To create a new softwareconfiguration that includes the SPR:
Install SPRs With DSM/SCM 141
1. From the Configuration Revisions page, select the configuration you are updating and clickCreate in the New Revision group. The new software revision page appears.
2. Select SPRs to be added to the current configuration and click Copy to.
Build the New RevisionAfter you have created a new software revision, prepare to install it on your target systems bybuilding it into an executable form:1. On the New software revision page, click Build/Apply to load the Build/Apply options page.2. Select Build (if not connected to an Expand network) or Build, apply & process snapshot (if
connected to an Expand network).3. Include in the activation package either only changed files or all files. If you are installing an
SPR, you can select changed files.4. In the Activation SYSnn: box, enter the current SYSnn (if no SYSGEN is required) or the new
SYSnn (if SYSGEN is required).
NOTE: If the Build/Apply Request page informs you that SYSGEN is required, check thatthe spooler is active and not 100 percent full before executing the Build/Apply request. At aTACL prompt, start SPOOLCOM and issue a COLLECT, STATUS command.
5. Select Scheduling, Output, SYSGEN, TSV Location, and File Placement tabs and configure asappropriate for your system. See the NonStop Software Essentials User's Guide or online help(Building and Applying a New Configuration topic) for more information about theseBuild/Apply Request options.
6. On the Build/Apply page, click Submit.7. Monitor the request from the request status page.
Print Operator Instructions From the Target Interface (ZPHITI)1. Make sure that spooler is active.2. On the DSM/SCM subvolume, enter:
RUN ZPHITI
The TI Logon screen appears.3. Enter your user ID/alias and password and press F1 to log on to the Target Interface.
The Main Menu appears.4. Enter 3 (Perform target activities) in the Selection number field and press F1.
The Target Menu - Select Target screen appears.5. In the Selection number field, enter the number corresponding to the logical target on which
the new software was applied and press F1.The Target Menu - Select Action screen appears.
6. In the Selection number field, enter 3 (Review operator instructions for the last apply completed)and press F1 to display the operator instructions.
7. Enter a printer location in the Print operator instructions field and press F9 to print the operatorinstructions.
Run ZPHIRNMDuring 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 runningprograms. 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.• Rename the new files, which have fabricated names, with their actual names.
142 Using DSM/SCM and NonStop Software Essentials to Install SPRs
1. At a TACL prompt, enter this command from the DSM/SCM subvolume:
> 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. When asked if you want to use a log file with the session, enter Y and press Enter.3. 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. Verify that ZPHIRNM ran successfully by reviewing the log file.5. If ZPHIRNM did not run successfully, correct the problem and rerun.
See the DSM/SCM User’s Guide for troubleshooting procedures and the DSM/SCMMessagesManual for a complete list of ZPHIRNM messages.
If Running INSTALL^TEMPLATES Is RequiredIf the operator instructions state that you should run INSTALL^TEMPLATES to update EMS templatefiles, you must be logged on as the super ID (255,255) user to run the INSTALL^TEMPLATES macro.This macro cannot be run with the NOWAIT option and takes approximately ten minutes to finish.Since the G06.10 RVU, if there is a resident template file in any of the input subvolumes, theINSTALL^TEMPLATES macro displays this error:
Invalid nonresident template file -- not key sequenced: $SYSTEM.ZTEMPL.NEWRES
*** INSTALL^TEMPLATES: Terminated due to error ***
HP recommends that you designate a unique subvolume to hold the template files created byINSTALL^TEMPLATES. When you follow the suggested procedure, a nonresident template file isnot present in ZTEMPL, and the error does not occur.1. Set the volume and subvolume to $SYSTEM.ZINSAIDS:
-> volume $system.zinsaids
2. Load the TACLMACS file:
-> load /keep 1/ TACLMACS
NOTE: If you run the INSTALL^TEMPLATES macro with no arguments, you are prompted toprovide required information. For information on the INSTALL^TEMPLATES arguments, printthe usage notes: -> volume $system.zinsaids -> load /keep 1/ TACLMACS ->install^templates /out outdev/ help where outdev is the name of the desiredoutput device.
3. Choose a location on $SYSTEM to keep updated template files:
If Running INSTALL^TEMPLATES Is Required 143
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. However, when thenew system is loaded, the old template files named in the last execution of INSTALL^TEMPLATESare opened instead of the new files. To use the new RTMPLATE and TEMPLATE EMS filescreated by DSM/SCM, enter this SCF ALTER command:-> ASSUME SUBSYS $ZZKRN -> ALTER, RESIDENT_TEMPLATES$SYSTEM.SYSTEM.RTMPLATE, & NONRESIDENT_TEMPLATES$SYSTEM.SYSTEM.TEMPLATE
The files newres and newnres are meant to be used as temporary names until the nextSYSGEN and system load.
The following error message might occur when running theINSTALL^TEMPLATES macro:
>$SYSTEM.SYSTEM.SCF /NAME $Z019,INV :INBUF.1,OUTV :OUTBUF.1/Current Nonresident template file is: $SYSTEM.TEMPLATE.NEWNRESTEMPLATE and NONRESIDENT files must be different: $SYSTEM.TEMPLATE.NEWNRES*** INSTALL^TEMPLATES: Terminated due to error ***
The message indicates that the template and nonresident files specifiedin the INSTALL^TEMPLATES command are identical to those on the currentsubvolume. The INSTALL^TEMPLATES macro tries to create the newres andnewnres files, but stops when it finds that these template files alreadyexist.
To correct the problem:1. Rename the current files:
tacl> rename newres, oldrestacl> rename newnres, oldnres
2. Run the INSTALL^TEMPLATES macro again and use the file names newres and newnres.This message indicates that the templates are successfully installed:
>$SYSTEM.SYS00.FUP /NAME $Z03M,INV :INBUF.1,OUTV :OUTBUF.1/File Utility Program - T6553D45 - (14APR2000) System \TINYCopyright Tandem Computers Incorporated 1981, 1983, 1985-2000SECURE ($SYSTEM.TEMPLATE.NEWRES,$SYSTEM.TEMPLATE.NEWNRES),"NUNU"*** INSTALL^TEMPLATES: Completed sucessfully ***
If a System Load Is RequiredIf OSM is installed and configured, use these instructions to load your RVU.
144 Using DSM/SCM and NonStop Software Essentials to Install SPRs
Halt the Processors1. If necessary, log on to the OSM Low-Level Link application.2. On the toolbar, select Processor Status to open the Processor Status dialog box.3. Select the processors to be halted.4. From the Processor Actions list, select Halt.5. Click Perform action.6. Click OK when asked if you are sure you want to halt.7. When the Action Status box confirms that all the processors have been halted, close the
Processor Status dialog box.8. Do not log off the OSM Low-Level Link.
Perform a System LoadA normal system load consists of loading the operating system from disk into the memory ofprocessor 0 or processor 1.See Chapter 9: “Loading This RVU”, for information on performing a system load.
Start Your Applications and ProcessesAfter you have reloaded the processors and the Processor Status screen shows all processorsexecuting the NonStop operating system, you can start your applications and processes. SeeChapter 10: “Resuming Normal Operations”.Verify that your system is up and running. See Chapter 9: “Loading This RVU”.
If a System Load Is Required 145
B Using DSM/SCM and Planner Interface to Install SPRsSPRs provide new features between RVUs or correct software problems from a previous RVU. Thisappendix 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 NonStopServers, for example) that the SPR can be installed on that specific J-series RVU.
See the J06.nn Release Version Update Compendium for this RVU and the Interactive UpgradeGuide 2 (IUG2) for information on SPRs that you might need to apply to your current RVU beforeupgrading to this RVU and connecting to a G-series or H-series system.
Tools for Managing SPRsAlways keep an SPR log file that lists which SPRs have been reviewed, selected, and installed onyour system:• Update the SPR log regularly to maintain accurate and current information about the SPRs
installed on your system.• Document the reasons for a decision not to install SPRs that have been issued for products you
run on your system.
Scout for NonStop ServersUsing Scout for NonStop Servers, you can display detailed information about RVUs, SPRs, andprerequisites for SPRs. You can also access:• Outage Prevention Notifications (OPNs)• Hotstuff messages• Support Notes• RVU (softdocs) and softdoc addendumsAfter researching available SPRs, you can download those you consider appropriate for yoursystem directly to your workstation and then use FTP to transfer downloaded SPRs to your server,or you can request tape delivery.
DSM/SCMDSM/SCM has automatic features that can help you keep records of SPRs. You can use theDSM/SCM Planner Interface to generate prepackaged reports, including reports that list:• The products on a system and the SPRs applied to those products• The SPRs that have been replaced by a specific SPR• The requisite SPRs for a selected SPRYou can also use the DSM/SCM Archive to export SPRs to different SYSnns.See the DSM/SCM User’s Guide for more information.
SPRNOTESYou can use SPRNOTES to research an SPR before installing it. Read the installation instructionsand 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
146 Using DSM/SCM and Planner Interface to Install SPRs
Keep a copy of each SPRNOTE and record the status of the related SPR. For example, recordwhether the SPR is not applicable, is already installed, or needs to be installed.
Install SPRs With DSM/SCMThe steps for using DSM/SCM to install SPRs are the same as those for installing a SUT.
Save the Current ConfigurationFirst, 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. At the SCF prompt, enter:
-> FUP INFO $SYSTEM.ZSYSCONF.CONF*
3. Save the current configuration by using a unique file name. At the SCF prompt, enter:
-> SAVE CONFIGURATION xx.yy
where xx.yy is a number from 0.0 through 99.99.
This example saves the current system configuration to the file $SYSTEM.ZSYSCONF.CONF1101:
-> SAVE CONFIGURATION 11.1The configuration file $SYSTEM.ZSYSCONF.CONF1101 has been created.
If you specify a configuration file that already exists, SCF asks you if you want to replace it. If youspecify that you do not want to replace the existing file, SCF does not overwrite the file. You mustenter another SAVE command to save the current configuration file.
Determine the Current SYSnnThere are several ways to record the current SYSnn subvolume on your system.You must use the current SYSnn subvolume if you need to fall back to your current RVU. You mustuse a different SYSnn subvolume to create a new software revision.1. At a TACL prompt, enter:
$SYSTEM SUPER 6> sysinfo
SYSINFO - T9268H01 - (01 OCT 2004) SYSTEM \ELI Date 04 May 2007, 22:00:18COPYRIGHT 2003 Hewlett-Packard Development Company, L.P.
System name \ELI EXPAND node number 033 Current SYSnn SYS01 System number 000000 Software release ID J06.04.00
2. Issue a TACL FILEINFO command on $system.*.osimage to list the SYSnn subvolumes onyour system and determine which one is open.
$SYSTEM.SYS00 CODE EOF LAST MODIFIED OWNER RWEP PExt SExtOSIMAGE 0 57354240 15DEC2007 9:57 255,255 NUNU 200 200
$SYSTEM.SYS01 CODE EOF LAST MODIFIED OWNER RWEP PExt SExt
Install SPRs With DSM/SCM 147
OSIMAGE 0 57393152 05APR2008 8:56 255,255 NUNU 200 200
3. At a TACL prompt, enter a STATUS 0,0 command to see which SYSnn subvolume is currentlybeing used:
3> status 0,0
System \ELI
Process Pri PFR %WT Userid Program file Hometerm 0,0 201 P R 000 255,255 $SYSTEM.SYS01.NMONTOR $YMIOP.#CLCI Swap File Name: $SYSTEM.#0
Receive the SPR Into the DSM/SCM Archive
Before Starting DSM/SCMStart TMF if it is not already running:
> TMFCOM START TMF
Bring the SPR Into the DSM/SCM Archive1. Start DSM/SCM if it is not already running:
> volume $dsmscm_vol.ZDSMSCM> RUN STARTSCM
2. Log on to the DSM/SCM Planner Interface.3. In the Software in Archive dialog box, click Receive software.
The Receive Software Request dialog box appears, and DSM/SCM automatically assigns thesoftware input a name based on information received from the SPR input. You can enter anew name if you want.
4. In the Receive Software Request dialog box, click Input source to display the Request SourceOptions dialog box.
5. If the SPR has been received on disk or has been restored from tape to disk, clickVolume.subvolume.
6. Enter the name of the distribution subvolume containing the SPR, and then click Add.7. If the SPR was received on tape, click Tape drive and select a tape drive from the list.8. Click OK.9. In the Receive Software Request dialog box, click Scheduling.10. Enter the time you want your Receive Software Request to run. The default option is for the
request to run immediately. If this is what you want, click OK.
Create a New Software Configuration That Includes the SPRAfter the SPR has been received into the Archive, you can copy it. To create a new softwareconfiguration that includes the SPR: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 configurationand click Copy to.
148 Using DSM/SCM and Planner Interface to Install SPRs
Build the New RevisionAfter you have created a new software revision, prepare to install it on your target systems bybuilding 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. Select Build (if not connected to an Expand network) or Build, apply & process snapshot (ifconnected to an Expand network).
3. Include in the activation package either only changed files or all files. If you are installing anSPR, you can select changed files.
4. In the Activation SYSnn: box, enter the current SYSnn (if no SYSGEN is required) or the newSYSnn (if SYSGEN is required).
NOTE: If the Build/Apply Request dialog box informs you that SYSGEN is required, checkthat 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.
5. Select Scheduling, Output, SYSGEN, TSV Location, and File Placement options and configureas appropriate for your system. See the DSM/SCM User’s Guide or online help (Building andApplying a New Configuration topic) for more information about these Build/Apply Requestoptions.
6. In the Build/Apply Request dialog box, click OK.7. When the Status window indicates that the request is done, select Window >Refresh.
This step updates the Software in Archive window to show the newly received software.8. Exit the DSM/SCM Planner Interface.
Print Operator Instructions From the Target Interface (ZPHITI)1. Make sure that spooler is active.2. On the DSM/SCM subvolume, enter:
RUN ZPHITI
The TI Logon screen appears.3. Enter your user ID/alias and password and press F1 to log on to the Target Interface.
The Main Menu appears.4. Enter 3 (Perform target activities) in the Selection number field and press F1.
The Target Menu - Select Target screen appears.5. In the Selection number field, enter the number corresponding to the logical target on which
the new software was applied and press F1.The Target Menu - Select Action screen appears.
6. In the Selection number field, enter 3 (Review operator instructions for the last apply completed)and press F1 to display the operator instructions.
7. Enter a printer location in the Print operator instructions field and press F9 to print the operatorinstructions.
Print Operator Instructions From the Target Interface (ZPHITI) 149
Run ZPHIRNMDuring 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 runningprograms. 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.• Rename the new files, which have fabricated names, with their actual names.1. At a TACL prompt, enter this command from the DSM/SCM subvolume:
> 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. When asked if you want to use a log file with the session, enter Y and press Enter.3. 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. Verify that ZPHIRNM ran successfully by reviewing the log file.5. If ZPHIRNM did not run successfully, correct the problem and rerun.
See the DSM/SCM User’s Guide for troubleshooting procedures and the DSM/SCMMessagesManual for a complete list of ZPHIRNM messages.
If Running INSTALL^TEMPLATES Is RequiredIf the operator instructions state that you should run INSTALL^TEMPLATES to update EMS templatefiles, you must be logged on as the super ID (255,255) user to run the INSTALL^TEMPLATES macro.This macro cannot be run with the NOWAIT option and takes approximately ten minutes to finish.Since the G06.10 RVU, if there is a resident template file in any of the input subvolumes, theINSTALL^TEMPLATES macro displays this error:
Invalid nonresident template file -- not key sequenced: $SYSTEM.ZTEMPL.NEWRES
*** INSTALL^TEMPLATES: Terminated due to error ***
HP recommends that you designate a unique subvolume to hold the template files created byINSTALL^TEMPLATES. When you follow the suggested procedure, a nonresident template file isnot present in ZTEMPL, and the error does not occur.1. Set the volume and subvolume to $SYSTEM.ZINSAIDS:
-> volume $system.zinsaids
2. Load the TACLMACS file:
-> load /keep 1/ TACLMACS
150 Using DSM/SCM and Planner Interface to Install SPRs
NOTE: If you run the INSTALL^TEMPLATES macro with no arguments, you are prompted toprovide required information. For information on the INSTALL^TEMPLATES arguments, printthe usage notes: -> volume $system.zinsaids -> load /keep 1/ TACLMACS ->install^templates /out outdev/ help where outdev is the name of the desiredoutput device.
3. Choose a location on $SYSTEM to keep updated template files:
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. However, when thenew system is loaded, the old template files named in the last execution of INSTALL^TEMPLATESare opened instead of the new files. To use the new RTMPLATE and TEMPLATE EMS filescreated by DSM/SCM, enter this SCF ALTER command:-> ASSUME SUBSYS $ZZKRN -> ALTER, RESIDENT_TEMPLATES$SYSTEM.SYSTEM.RTMPLATE, & NONRESIDENT_TEMPLATES$SYSTEM.SYSTEM.TEMPLATE
The files newres and newnres are meant to be used as temporary names until the nextSYSGEN and system load.
The following error message might occur when running theINSTALL^TEMPLATES macro:
>$SYSTEM.SYSTEM.SCF /NAME $Z019,INV :INBUF.1,OUTV :OUTBUF.1/Current Nonresident template file is: $SYSTEM.TEMPLATE.NEWNRESTEMPLATE and NONRESIDENT files must be different: $SYSTEM.TEMPLATE.NEWNRES*** INSTALL^TEMPLATES: Terminated due to error ***
The message indicates that the template and nonresident files specifiedin the INSTALL^TEMPLATES command are identical to those on the currentsubvolume. The INSTALL^TEMPLATES macro tries to create the newres andnewnres files, but stops when it finds that these template files alreadyexist.
To correct the problem:1. Rename the current files:
tacl> rename newres, oldrestacl> rename newnres, oldnres
2. Run the INSTALL^TEMPLATES macro again and use the file names newres and newnres.This message indicates that the templates are successfully installed:
>$SYSTEM.SYS00.FUP /NAME $Z03M,INV :INBUF.1,OUTV :OUTBUF.1/File Utility Program - T6553D45 - (14APR2000) System \TINYCopyright Tandem Computers Incorporated 1981, 1983, 1985-2000
If Running INSTALL^TEMPLATES Is Required 151
SECURE ($SYSTEM.TEMPLATE.NEWRES,$SYSTEM.TEMPLATE.NEWNRES),"NUNU"*** INSTALL^TEMPLATES: Completed sucessfully ***
If a System Load Is RequiredIf OSM is installed and configured, use these instructions to load your RVU.
Halt the Processors1. If necessary, log on to the OSM Low-Level Link application.2. On the toolbar, select Processor Status to open the Processor Status dialog box.3. Select the processors to be halted.4. From the Processor Actions list, select Halt.5. Click Perform action.6. Click OK when asked if you are sure you want to halt.7. When the Action Status box confirms that all the processors have been halted, close the
Processor Status dialog box.8. Do not log off the OSM Low-Level Link.
Perform a System LoadA normal system load consists of loading the operating system from disk into the memory ofprocessor 0 or processor 1.See Chapter 9: “Loading This RVU”, for information on performing a system load.
Start Your Applications and ProcessesAfter you have reloaded the processors and the Processor Status screen shows all processorsexecuting the NonStop operating system, you can start your applications and processes. SeeChapter 10: “Resuming Normal Operations”.Verify that your system is up and running. See Chapter 9: “Loading This RVU”.
152 Using DSM/SCM and Planner Interface to Install SPRs
C Installing SWID and DSM/SCM PVU Using NonStopSoftware 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. (DSM/SCM uses SWID to determine if a file haschanged by a method called fingerprinting. If an existing file has a different fingerprint from a newer file, the newerversion replaces the existing file.)
Alerts• “Determine the Product Version of DSM/SCM on the Host System” and “Determine the Product
Version of DSM/SCM on the Client”.• Save the current configuration database. (See “Save the Current Configuration File
(CONFxxyy)” (page 45)).• Keep the startup TACL windows, the EMS Event Stream window, and the DSM/SCM client
interface windows open whenever you are performing a Build/Apply. Otherwise, Build/Applyerrors will result.
• If you receive an error indication in the Request Status window, you might have to re-initiatethe Build/Apply. See the DSM/SCM Messages Manual to learn the nature and severity ofthe problem.
Determine the Product Version of DSM/SCM on the Host SystemTo determine which product version of DSM/SCM is currently installed on your system, use theVPROC command to determine the product version of TAEXE (Apply product of DSM/SCM) andCBEXE (Build product of DSM/SCM).At a TACL prompt, enter:
> volume $dsmscm_vol.ZDSMSCM> vproc taexe> vproc cbexe
If your VPROC commands do not display the version for this RVU, install the correct DSM/SCMproduct version by following the procedures in “Copy (RESTORE) the H02 DSM/SCM ProductVersion to Disk (If Necessary)” (page 154).The DSM/SCM version for this RVU is ACY.
Determine the Latest SWID ProductUsing the VPROC command, identify the SWID SPR.The SWID version for this RVU is AAV.
Determine the Product Version of DSM/SCM on the ClientTo determine which product version of DSM/SCM client software is installed, start the DSM/SCMPlanner Interface. Before prompting you to log on, the About DSM/SCM window briefly displaysversion information. For example:
Alerts 153
To install the DSM/SCM client, see “Install the NonStop Software Essentials Client” (page 159).
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, ata 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 containingthis RVU.
Receive the H02 SWID and DSM/SCM SPRs1. Start TMF and DSM/SCM if they are not already running:2. > TMFCOM START TMF > VOLUME $dsmscm_vol.ZDSMSCM > RUN STARTSCM3. Log on to NonStop Software Essentials.4. Click the Receive Software link on the Home Page.5. Under Software name, select Provided by planner and enter a name for the H02 DSM/SCM
and SWID SPRs, up to 17 characters.6. Click the Input Source tab. NonStop Software Essentials displays the input source options.7. Select Subvolume.8. In the Find/Add text box, enter each distribution subvolume for the DSM/SCM files that you
specified earlier in the RESTORE command:
$DSMSCM.E6031H02$DSMSCM.E9298H02
Your Receive Software Input Source tab should look similar to this:
154 Installing SWID and DSM/SCM PVU Using NonStop Software Essentials Client Software
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 SPRs1. In the Configuration Revisions page, select the target system being upgraded and the current
revision of the system being upgraded. Select New software revision.The New Software Revision page is loaded with the last software revision that was built forthe target in the new revision table.
2. Load the software you just received into the source table and click Copy to.The set of products you received into the archive: T6031 and T9298 are copied from theArchive to the new software revision.
Create a New Software Revision for H02 DSM/SCM and SWID SPRs 155
3. From the New software revision table, verify that the new version of DSM/SCM and SWIDare included in the new software revision.
4. 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. Click OK to save your changes to the revision notes
Build and Apply the DSM/SCM H02 Software Product RevisionThe 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 theApply request is finished, a snapshot is automatically created and returned to the host. Becauseyou are building and applying only a few files, it should take less than an hour before the Buildand Apply requests are finished and the snapshot is returned. When the Build and Apply requestsare finished, the new software is placed in the current SYSnn subvolume.1. On the New software revision page, click Build/Apply to display the options for your
Build/Apply.2. Edit the instructions to the operator to provide the current SYSnn number and then click OK.3. Complete the Build/Apply Request dialog box:
a. Under Perform steps, select Build, apply & process snapshot.b. Enter the current SYSnn in the Activation SYSnn text box (because no SYSGEN is required).c. Click Submit Build/Apply.
156 Installing SWID and DSM/SCM PVU Using NonStop Software Essentials Client Software
NonStop Software Essentials runs the Build/Apply requests and displays a Status pagethat is automatically updated at regular intervals.
4. 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.
5. To confirm that the Build and Apply tasks finish successfully and that a snapshot has beenreceived into the host database, wait until the status shows that all activities are complete.
Run the INSTALL^TEMPLATES MacroEMS templates are used by EMS to format EMS messages. After running ZPHIRNM, and if notifiedto do so by DSM/SCM, run the INSTALL^TEMPLATES TACL macro to install DSM/SCM EMStemplates in their proper locations.
NOTE: The files newres and newnres are used as temporary names until the next SYSGENand system load.
The INSTALL^TEMPLATES macro is located in the $SYSTEM.ZINSAIDS subvolume and invokes theTEMPLI program to build new resident and nonresident EMS template files.You must be logged on as a super.super (255, 255) user to run the INSTALL^TEMPLATES macro.This macro cannot be run with the NOWAIT option and takes approximately ten minutes to finish.For detailed instructions on running the INSTALL^TEMPLATES macro, including troubleshootinginformation, see “If Running INSTALL^TEMPLATES Is Required” (page 143).
Run the INSTALL^TEMPLATES Macro 157
Restart ApplicationsYou can now start your application software. Follow your site’s procedures for executing the systemconfiguration and startup (command) files to accomplish this.DSM/SCM is often started automatically by a system command file. If not, you must start DSM/SCMmanually as described next.
Before Starting DSM/SCM1. Check that TMF is started:
> TMFCOM STATUS TMF
2. Verify your current configuration against the cold start configuration in PATHHOST (orPATHTARG) to check that the current configuration reflects all changes you have made.
3. If necessary, run the PATHCOLD macro from the ZDSMSCM subvolume to cold start thePathway configuration.
Start DSM/SCM1. Run the STARTSCM macro from the ZDSM/SCM subvolume to start DSM/SCM:
> 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 alwayspaused, no action is necessary.
PATHWAY CONTROL FILE DATED: 21 APR 2006, 03:52:16$Z03N: WARN - *1079* SERVER CB-001, NO STATIC SERVERS DEFINED$Z03N: WARN - *1079* SERVER IS-001, NO STATIC SERVERS DEFINED$Z03N: WARN - *1079* SERVER MISERVER, NO STATIC SERVERS DEFINED$Z03N: SERVER OM-001, STARTED$Z03N: SERVER SM-001, STARTED$Z03N: SERVER SM-T-001, STARTED
$Z03N: SERVER T9154-HELP-SERV, STARTED$Z03N: WARN - *1079* SERVER TA-001, NO STATIC SERVERS DEFINED$Z03N: WARN - *1079* SERVER TISERVER, NO STATIC SERVERS DEFINED$Z03N: WARN - *1079* SERVER US-001, NO STATIC SERVERS DEFINED$Z03N: TCP TCP-H, STARTED$Z03N: TCP TCP-T, STARTED
2. If necessary, press Enter to have STARTSCM run the IPM6031 TACL macro automatically. Thisstep takes several minutes.
STARTSCM: A new version of DSM/SCM has been installed and IPM6031 needs to be run. You can either exit and run IPM6031manually or continue and IPM6031 will be run for you.Enter <CR> to continue or BREAK to exit.
158 Installing SWID and DSM/SCM PVU Using NonStop Software Essentials Client Software
Verify that the Latest SPR of DSM/SCM is InstalledTo verify that the appropriate version of DSM/SCM is currently installed on your system, use theVPROC command to display the product version of TAEXE (Apply product of DSM/SCM) andCBEXE (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 ACY.
Verify That SWID Is InstalledThis example shows the H02 product version of SWID. Use the VPROC command(\DRP08.$SYSTEM.SYSTEM 101> vproc swid).The SWID version for this RVU is AAV.
Recovery for Problems While Installing the H02 Version of DSM/SCMIf you encounter problems while installing the H02 version of DSM/SCM, see the DSM/SCMUser’s Guide.
If NonStop Errors Are DisplayedSee the DSM/SCM EMS Messages manual for information regarding the error message and theDSM/SCM User’s Guide for information on deleting a Build/Apply request.
Cancel Pending Build/Apply Requests
NOTE: If you inadvertently close the Status page, reopen it by clicking on the Request Name linkon the Request List page.
Click the Cancel button.The cancel request action takes a few minutes to finish.
NOTE: If you cannot cancel the Build request through NonStop Essentials, use the DSM/SCMTarget Interface (ZPHITI) to cancel the request. See the NonStop Software Essentials User’s Guideand online help for more information.
NOTE: If you inadvertently close the Status dialog box, reopen it by selecting Requests> Requestslist and then double-clicking the request.
Install the NonStop Software Essentials ClientNOTE: See the NonStop Software Essentials Installation and Quick Start Guide.
If you have to fall back, you can use the newly installed client software.
Determine the Product Version of NonStop Software Essentials on the ClientAccess Help>About HP SIM from an HP SIM window to display all the versions of HP SIM pluginsoftware.
Recovery for Problems While Installing the H02 Version of DSM/SCM 159
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 clientversion is available only on the SUT unless you have ordered new system consoles.
• Always install the latest SWID PVU at the same time you install a new DSM/SCM PVU to avoid a fingerprint ormismatched file problem. (DSM/SCM uses SWID to determine if a file has changed by a method called fingerprinting.If an existing file has a different fingerprint from a newer file, the newer version replaces the existing file.) Yournewly shipped system will have the latest SWID SPR.
• DSM/SCM is not installed and not supported on 64-bit consoles. If you have a Windows 2008 (64-bit) console,use the instructions for installing SWID and DSM/SCM using NonStop Software Essentials (“Using DSM/SCM andNonStop Software Essentials to Install SPRs” (page 139).
Alerts• “Determine the Product Version of DSM/SCM on the Host System” and “Determine the Product
Version of DSM/SCM on the Client”.• Save the current configuration database. (See “Save the Current Configuration File
(CONFxxyy)” (page 45)).• Keep the startup TACL windows, the EMS Event Stream window, and the DSM/SCM client
interface windows open whenever you are performing a Build/Apply. Otherwise, Build/Applyerrors will result.
• If you receive an error indication in the Request Status window, you might have to re-initiatethe Build/Apply. See the DSM/SCM Messages Manual to learn the nature and severity ofthe problem.
Determine the Product Version of DSM/SCM on the Host SystemTo determine which product version of DSM/SCM is currently installed on your system, use theVPROC command to determine the product version of TAEXE (Apply product of DSM/SCM) andCBEXE (Build product of DSM/SCM).At a TACL prompt, enter:
> volume $dsmscm_vol.ZDSMSCM> vproc taexe> vproc cbexe
If your VPROC commands do not display the version for this RVU, install the correct DSM/SCMproduct version by following the procedures in “Copy (RESTORE) the H02 DSM/SCM ProductVersion to Disk (If Necessary)” (page 154).The DSM/SCM version for this RVU is ACY.
Determine the Latest SWID ProductUsing the VPROC command, identify the SWID SPR. The SWID version for this RVU is AAV.
Determine the Product Version of DSM/SCM on the ClientTo determine which product version of DSM/SCM client software is installed, start the DSM/SCMPlanner Interface. Before prompting you to log on, the About DSM/SCM window briefly displaysversion information. For example:
160 Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software
You can also bring up the above dialog box with Help/About; this method keeps the windowopen until you close it.To install the DSM/SCM client, see “Install the NonStop Software Essentials Client” (page 159).
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, ata 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 containingthis RVU.
Receive the H02 SWID and DSM/SCM SPRs1. Start TMF and DSM/SCM if they are not already running:2. > TMFCOM START TMF > VOLUME $dsmscm_vol.ZDSMSCM > RUN STARTSCM3. Select Start>Programs>dsm_scm>DSMSCM to log on to the DSM/SCM Planner Interface.4. In the Software in Archive dialog box, select Receive software.
DSM/SCM displays the Receive Software Request dialog box.5. Under Software name, select Provided by planner and enter a name for the H02 DSM/SCM
and SWID PVUs up to 17 characters.6. Under Options, click Input source.
DSM/SCM displays the Request Source Options dialog box.7. Select Volume.subvolume.8. In the Add text box, enter each distribution subvolume for the DSM/SCM files that you specified
earlier in the RESTORE command:
$DSMSCM.E6031H02
$DSMSCM.E9298H02
Your Request Source Options dialog box should look similar to this:
Copy (RESTORE) the H02 DSM/SCM Product Version to Disk (If Necessary) 161
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 appearsas Complete, and then close the Status window. For example:
162 Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software
11. Select Window>Refresh to update the Software in Archive dialog box to include the receivedsoftware.
Create a New Software Revision for H02 DSM/SCM and SWID SPRs1. 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 thatwas built for the target. Allow several minutes for the dialog box to appear.
2. In the Software in Archive dialog box, select the DSM/SCM software you just received andclick Copy to.The DSM/SCM files are copied from the Archive to the new software revision.
3. From the New software revision dialog box, verify that the new version of DSM/SCM andSWID are included in the new software revision.
4. 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 06/07/08: DSM/SWID
c. Click OK to add a written history of revisions to existing notes.
Build and Apply the DSM/SCM H02 Software Product RevisionThe 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 theApply request is finished, a snapshot is automatically created and returned to the host. Becauseyou are building and applying only a few files, it should take less than an hour before the Build
Create a New Software Revision for H02 DSM/SCM and SWID SPRs 163
and Apply requests are finished and the snapshot is returned. When the Build and Apply requestsare 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 thistime, 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. The name assigned to theBuild/Apply request appears after Request name.
2. Click Edit instructions to display the Planner Instructions box.3. Edit the instructions to provide the current SYSnn number, and then click OK.4. Complete the Build/Apply Request dialog box:
a. Under Perform steps, select Build, apply & process snapshot.b. Enter the current SYSnn in the Activation SYSnn text box (because no SYSGEN is required).c. Click OK.
DSM/SCM runs the Build/Apply requests and displays a Status dialog box that isautomatically updated at regular intervals.
5. 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.
6. To confirm that the Build and Apply tasks finish successfully and that a snapshot has beenreceived into the host database, wait until the status shows that all requests are complete.
7. Select Window>Refresh.The Configurations Revision dialog box is refreshed and shows the new software configurationrevision containing the H02 DSM/SCM SPR.
164 Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software
Rename the Applied DSM/SCM H02 Files By Running ZPHIRNM1. 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. When asked if you want to use a log file with the session, enter Y.4. When prompted, enter a file name for the log file.
ZPHIRNM displays this message:
Log file, filename, was successfully created.
ZPHIRNM processes the file renaming.5. Verify that ZPHIRNM ran successfully by reviewing the specified log file. For an example of
output, see“ZPHIRNM” (page 86).
Run the INSTALL^TEMPLATES MacroEMS templates are used by EMS to format EMS messages. After running ZPHIRNM, and if notifiedto do so by DSM/SCM, run the INSTALL^TEMPLATES TACL macro to install DSM/SCM EMStemplates in their proper locations.
NOTE: The files newres and newnres are used as temporary names until the next SYSGENand system load.
The INSTALL^TEMPLATES macro is located in the $SYSTEM.ZINSAIDS subvolume and invokes theTEMPLI program to build new resident and nonresident EMS template files.You must be logged on as a super.super (255, 255) user to run the INSTALL^TEMPLATES macro.This macro cannot be run with the NOWAIT option and takes approximately ten minutes to finish.For detailed instructions on running the INSTALL^TEMPLATES macro, including troubleshootinginformation, see “If Running INSTALL^TEMPLATES Is Required” (page 143).
Restart ApplicationsYou can now start your application software. Follow your site’s procedures for executing the systemconfiguration and startup (command) files to accomplish this.DSM/SCM is often started automatically by a system command file. If not, you must start DSM/SCMmanually as described next.
Before Starting DSM/SCM1. Check that TMF is started:
> TMFCOM STATUS TMF
2. Verify your current configuration against the cold start configuration in PATHHOST (orPATHTARG) to check that the current configuration reflects all changes you have made.
3. If necessary, run the PATHCOLD macro from the ZDSMSCM subvolume to cold start thePathway configuration.
Start DSM/SCM1. Run the STARTSCM macro from the ZDSMSCM subvolume to start DSM/SCM:
Rename the Applied DSM/SCM H02 Files By Running ZPHIRNM 165
> 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 alwayspaused, no action is necessary.
PATHWAY CONTROL FILE DATED: 21 APR 2006, 03:52:16$Z03N: WARN - *1079* SERVER CB-001, NO STATIC SERVERS DEFINED$Z03N: WARN - *1079* SERVER IS-001, NO STATIC SERVERS DEFINED$Z03N: WARN - *1079* SERVER MISERVER, NO STATIC SERVERS DEFINED$Z03N: SERVER OM-001, STARTED$Z03N: SERVER SM-001, STARTED$Z03N: SERVER SM-T-001, STARTED
$Z03N: SERVER T9154-HELP-SERV, STARTED$Z03N: WARN - *1079* SERVER TA-001, NO STATIC SERVERS DEFINED$Z03N: WARN - *1079* SERVER TISERVER, NO STATIC SERVERS DEFINED$Z03N: WARN - *1079* SERVER US-001, NO STATIC SERVERS DEFINED$Z03N: TCP TCP-H, STARTED$Z03N: TCP TCP-T, STARTED
2. If necessary, press Enter to have STARTSCM run the IPM6031 TACL macro automatically. Thisstep takes several minutes.
STARTSCM: A new version of DSM/SCM has been installed and IPM6031 needs to be run. You can either exit and run IPM6031manually or continue and IPM6031 will be run for you.Enter <CR> to continue or BREAK to exit.
Verify that the Correct SPR of DSM/SCM is InstalledTo verify that the appropriate product 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 correct DSM/SCM SPR for this RVU is ACY.
Verify That SWID Is InstalledUsing the VPROC command, identify the SWID SPR. The SWID version for this RVU is AAV.
Recovery for Problems While Installing the H02 Version of DSM/SCMIf you encounter problems while installing the H02 version of DSM/SCM, see the DSM/SCMUser’s Guide.
166 Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software
If NonStop Errors Are DisplayedSee the DSM/SCM EMS Messages manual for information regarding the error message and theDSM/SCM User’s Guide for information on deleting a Build/Apply request.
Cancel Pending Build/Apply Requests1. Select the request to be canceled.2. 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, usethe DSM/SCM Target Interface (ZPHITI) to cancel the request. See the DSM/SCM User’sGuide and online help for more information.
3. Using NonStop Software Essentials, rename the old software packages:a. Select the software package to load it into the work panel.b. In the Software name box, edit the name so that another operator will know it is a
DSM/SCM input that should not be used to build a new software revision.c. Click Save.
Install the DSM/SCM Client From ZDSMSCMNOTE: Before you begin, back up your current DSM/SCM folder to save the configurationinformation and the Planner Interface version.Check that unnecessary PC programs are not running before you begin the DSM/SCM clientinstallation and that no DSM/SCM Build or Applies are in progress.
If you have to fall back, you can use the newly installed client software.
NOTE: HP recommends that both the DSM/SCM product version (T6031G02/H02) andDSM/SCM client be at the same version level at all times. To make sure you have the right client,check the version using VPROC. Install it if necessary.
Determine Your DSM/SCM Client Software VersionTo determine which version of DSM/SCM client software is installed, start the DSM/SCM PlannerInterface. Before prompting you to log on, the About DSM/SCM window briefly displays versioninformation. See “Determine the Product Version of DSM/SCM on the Host System” (page 153).
Determine the Current IP Address and Port NumberWhen you install DSM/SCM client software, you are prompted to enter the IP address of the hostsystem with which DSM/SCM communicates and the IP port number for the DSM/SCM Winsockservice.1. If the DSM/SCM client software on your system console is configured to communicate with a
host system, determine the configured IP address and port number:2. Start Windows Explorer. Open My Computer if not already open.3. Double-click the hard drive icon to display its contents.4. Open the DsmScm folder to display its contents.5. In the Contents pane, double-click dsmscm.ini.
Notepad opens the DSM/SCM initialization file. For example:
Install the DSM/SCM Client From ZDSMSCM 167
6. Make a note of the IP address and port number.7. Close the dsmscm.ini file.
Copy the ZDSMSCM Client File From the Host1. 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. Enter: cd c:\3. If a DSMSCM directory does not exist, enter the following at the C:\ prompt to create it:
mkdir DSMSCM
4. At the C:\ prompt, enter: cd DSMSCM5. Enter: ftp <ip-address>, where ip-address is the IP address of your NonStop server.
For example, ftp 192.231.36.10.An example response is:Connected to 192.231.36.10. 220 osmlanx FTP SERVER T9552H02 (Version H02 TANDEM 03MAY2006) readyUser (192.231.36.10: (none)): super.super331 Password required for SUPER.SUPER.
6. Enter the super.super password.An example response is:230 User SUPER.SUPER logged in. OSS API enabled
7. At the ftp> prompt, enter: quote guardian.An example response is:257 Guardian API enabled
8. Enter: bin.An example response is:200 Type set to I
9. Enter: cd $DSMSCM.ZDSMSCM.An example response is:250 CWD command successful
10. Enter: get zdsmexe zdsm.exe.An example response is:
168 Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software
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 orC:\DSMJ06nn.
12. Double click on zdsm.exe to expand the files into the desired folder.
Install the DSM/SCM Client Software1. Using Windows Explorer, double-click Setup.exe.
A DSM/SCM Setup screen appears, and an Enter Object Manager Server Class dialog boxappears with the default OM-001.
2. Click Next to accept the default.The Enter Software Product Group Type (shared or private) dialog box appears.
3. Click Next to accept the default (private) or type in shared and click Next.
Install the DSM/SCM Client From ZDSMSCM 169
NOTE: Private software product groups can be used only by the planner who creates thegrouping. Shared software product groups can be used by other planners. For more informationon these options, see the DSM/SCM User’s Guide. (NonStop Software Essentials only supportsshared 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. Check that WINSOCK is selected. Click Next.The Choose Destination Location dialog box appears with the default path displayed, basedon your Windows operating system:
170 Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software
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 “Determinethe Current IP Address and Port Number” (page 167)), and click Next.
NOTE: If DSM/SCM is not currently configured to communicate with a host system, acceptthe default IP address. You can always change this value later by editing the dsmscm.ini file.
You are now prompted to enter an IP port number:
Install the DSM/SCM Client From ZDSMSCM 171
8. Enter the IP port number for the Winsock service (see “Determine the Current IP Address andPort Number” (page 167)), and click Next.
NOTE: If DSM/SCM is not currently configured to communicate with a host system, acceptthe default IP port number. You can always change this value later by editing the dsmscm.inifile.
You are now prompted to enter the host system name.
9. Enter the host system name (or \noname if DSM/SCM is not currently configured tocommunicate with a host system), and click Next to continue.You are asked if you would like to run DSM/SCM.
172 Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software
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 theStart>Programs>DSM_SCM submenu. For example:
Install the DSM/SCM Client From ZDSMSCM 173
E Updating SWAN Concentrator CLIP FirmwareIf necessary, you can update the SWAN or SWAN 2 concentrator CLIP firmware after you havecompleted a system load of the new RVU.See either the SWAN Concentrator Installation and Support Guide or the SWAN 2 ConcentratorInstallation and Support Guide.
174 Updating SWAN Concentrator CLIP Firmware
AcronymsThis 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 processCRU Customer replaceable unit.DHCP Dynamic Host Configuration Protocol.DLL Dynamic link library.DSM/SCM Distributed Systems Management/Software Configuration Manager.DSV Distribution subvolume.EFI Extensible firmware interface.EMS Event Management System.FCDM Fibre Channel disk module.FCSA Fibre Channel ServerNet adapter.FPGA Field programmable gate array.FRU Field replaceable unit.G4SA Gigabit Ethernet 4–port ServerNet adapter.G4SA Gigabit Ethernet 4-port ServerNet adapter.HP SUM Smart Update Manager.HSS halted-state services.iLO Integrated Lights-Out.inetd A server daemon that runs in the OSS environment.IOAM I/O adapter module.IOMF2 I/O Multifunction 2.ISEE Instant Support Enterprise Edition.IUG2 Interactive Upgrade Guide 2.KMSF Kernel-Managed Swap Facility.LUN Logical unit number.ME Maintenance Entity.NSC NonStop System Console.NTL NonStop Technical Library.NTL NonStop Technical Library.OA Onboard Administrator.OSM Open System Management.OSS Open System Services.OSS Open System Services.PAL Programmable array logic.
175
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.SPR Software Product Revision.SS7 Signaling System Number 7.SSL Secure Socket Layer.SUT Site update tape.SWAN ServerNet wide area network.SWAN 2 ServerNet wide area network 2.SWID Software identification (tool).TACL Tandem Advanced Command Language.TMF Transaction Management Facility.TMF Transaction Manager Facility.TRSA Token Ring ServerNet adapter.TSV Target subvolume.VIO Versatile I/O.
176 Acronyms
Index
Symbols$SYSTEM.ZTCPIP, 100$SYSTEM.ZTCPIP subvolume, 84$ZCDB, 20$ZPLS, 31
AAUDITTRAILBUFFER parameter, DP2 and RDF performance,
103
BBack up files
backing up important files before upgrading, 44ZTCPIP subvolume, 84
Build process, DSM/SCM, 61, 75Build/Apply request, defined, 19
CCBEXE product
determining version on host system, 153, 160verifying version, 159, 166
CIIN file, 93, 133disabled, 93, 133
CLCI sessions, 95CLIM
compatibility with host RVUs, 30, 32fallback procedure, 114firmware, 28installing CLIM software, 20
CNSL session, 95Commands
RELOAD, 96, 134STATUS TAPE, 50
CONFIG filesaving, 45, 140, 147use in loading the previous RVU, 133use in loading the system, 93
DDSM/SCM
build process, 61, 75prepackaged reports, 139, 146Target Interface, 21
EEasySetup, 55, 68
FFabricated file names, 19Fallback
summary of major tasks, 20ZPHIRNM, 111
Fibre Channel ServerNet Adapter (FCSA) , 26Firmware
managing, 22
GGigabit 4-port ServerNet Adapter (G4SA), 27
Iinetd process, 102INITSTAT, 102INSTALL^TEMPLATES
instructions, 143, 150using with DSM/SCM, 157, 165
Installing the DSM/SCM client from ZDSMSCM, 159, 167Interoperability
audit format issues, 52SPRs for NonStop BladeSystems and NonStop Systems,
52iTP WebServer considerations, 104
KKernel-managed swap files, 51
LLoading the J-series RVU, 89Loading the system, 93, 133, 145, 152
Mmerge_whatis, 99Migration issues, 30MR-Win6530 terminal emulator
startup windows on, 95
NNew software revision, DSM/SCM, 72New software revision, NonStop Software Essentials, 58NonStop Cluster switch firmware, 28NonStop SOAP 4 considerations, 104NonStop Software Essentials, changing profile information,
59NonStop TCP/IP configuration files, 100NonStop TCP/IPv6 files, 85NSKCOM, 51
OOSS
EasySetup , 103Root Name Server $ZPNS, 58, 72
PPcleanup utility, 99Planner Interface, changing profile information, 73PORTCONF file, 101Post-installation
configuring OSS, 102configuring RDF, 103configuring SMF, 103updating TCP/IP configuration files, 100
PREVIEW mode, 87
177
Processor type in CONFTEXT file, 20Profiles, target, changing information, 59, 73PROTOCOL file
configuration file location, 101
RRDF, 103RELOAD command, 96, 134Remote Database Facility, 103
SSCF
testing the tape subsystem, 50verifying critical processes, 49verifying disks, 49
Scout for NonStop Servers, 14ServerNet adapter firmware, 25SERVICES file, 101SMF, interoperability and configuration, 103SOAP 4 see NonStop SOAP 4Software revision, 19Spooler
backing up, command for, 86checking status of collector, 51COLLECT, STATUS command, 63, 77, 105, 142, 149DRAIN command, 86draining, 44
SPRNOTES, 140, 146SPRs
interoperability, 52Status dialog box, reopening, 83, 159SUT, maximum size of, 14SWAN and SWAN 2 concentrator firmware, 28Swap file space, checking , 51SYSnn subvolumes
listing, 45System configuration file, 140, 147System console DVD version, 15
TT0895V02, 18T6031G02, 18T6031G02/H02, 18T6031H01, 18T6031H02, 17TACL RELOAD command, 21, 96TAEXE, 153, 159, 160, 166Target subvolumes (TSVs), 19Target systems, changing profile information, 59, 73TEMPLI program, 157, 165TRM2000, 14
UUpdating firmware
user-updateable, 22
VVPROC command, 153, 160
ZZcccGP files, 84ZCNFDEFS, 84ZINSAIDS subvolume, 157, 165ZMODGP, 20ZMODGP, in Preview mode, 86ZPHIRNM
PREVIEW mode, 87reactivating previous software revision, 111running, 84, 142, 150
ZPHITIcanceling a Build/Apply request, 83, 167starting, 105
178 Index