J06.15 Software Installation and Upgrade Guide

Transcription

1 J06.15 Software Installation and Upgrade Guide HP Part Number: Published: May 2015 Edition: J06.15 RVU

2 Copyright 2015 Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor s standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not 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.

3 Contents About This Document...11 Supported RVUs...11 Intended Audience...11 New and Changed Information in This Edition...11 What This Guide Does Not Cover...11 Notation Conventions...12 General Syntax Notation...12 Related Information...12 Publishing History...13 HP Encourages Your Comments Overview of Installing This RVU...14 SUT on DVD...14 CLIM Software for This RVU...14 Disk Space Requirements...14 Operational Differences Between This RVU and H-Series RVUs...14 Investigating a J-Series RVU...14 NonStop System Console Requirements...15 Console Requirements for Dedicated Service LANs...15 Updating System Consoles (Optional)...15 NonStop Software Essentials and Console Requirements...15 Using OSM With This RVU...16 OSM Server-Based Component...16 OSM Client-Based Components...16 Using DSM/SCM and NonStop Software Essentials With This RVU...17 NonStop Software Essentials and This RVU...17 DSM/SCM and This RVU...18 OSBUILD SPR...18 DSM/SCM and Public DLLs...18 DSM/SCM and OSS...18 Upgrading the NonStop Software Essentials Client...19 Upgrading the DSM/SCM Client (Planner Interface) and the T6031H02 PVU...19 Summary of Software Installation Tasks...19 Check or Alter the CONFTEXT File Before Installing This RVU SUT...20 Installing CLIM Software...21 Backing Out the DSM/SCM Revision...21 Managing Microcode and Firmware...21 Installation, Migration, and Fallback...21 Perform an RVU Upgrade on a Node Managing Microcode and Firmware...22 Managing BladeCluster Software and Firmware Requirements...22 Managing ME Firmware and ME FPGA Firmware...22 Updating ME Firmware...22 Updating ME FPGA...24 Managing OA Firmware for the c7000 Enclosure...24 Managing Server Blade Firmware and Blade Element Firmware...24 Managing ServerNet Adapter Firmware...25 Managing SWAN and SWAN 2 Concentrator Firmware...28 Managing NonStop Cluster Switch Firmware...28 Managing CLIM Firmware and Software...29 Managing S-Series Interoperability Firmware...30 Contents 3

4 3 Installation, Migration, and Fallback Considerations for This RVU...31 J Compiling C++ Programs to Run on RVUs Earlier Than J SQL/MX Versioning Feature Removed...31 CLIM...31 J AF_UNIX Release 2 Migration and Fallback...32 Migrating to AF_UNIX Release Falling Back to An Earlier Version of AF_UNIX...33 CLuster I/O Module (CLIM) Software Compatibility...33 J CLuster I/O Module (CLIM) Software Compatibility...34 DSM/SCM Upgrade Issues/Interoperability SPR Requirements...34 J Falling Back to ilo Firmware T0848AAA...34 DSM/SCM Upgrade Issues/Interoperability SPR Requirements...35 J NonStop SQL/MX...35 J SQL/MX Requires JDBC T2 Driver...35 BladeCluster Solution Multi-Zone Support...35 J NonStop SOAP New CLuster I/O Module (CLIM) Storage Devices...36 Other CLIM and CIP Changes...36 Hardware and Networking...36 New Operating System Features...36 TMF itp WebServer Expand Enhancements...36 J Changes to SSOCLIM Privilege Requirement...37 J HP SUM...37 Considerations for Fallback to J J Safeguard...37 Considerations for Fallback to J Performance Tuning Requirements...37 Core License File...37 Migrating a NonStop BladeSystem NB50000c to an NB54000c or NB50000c-cg to an NB54000c-cg...37 Upgrading a NonStop BladeSystem NB54000c or NB54000c-cg to J06.13 or Later RVUs...38 HP NonStop Software Essentials...38 IB CLIM Fallback Considerations...38 EXTDECSL...38 TNS/E ECOBOL...38 J Halt and Hard Reset Processors When Upgrading to J HP Power Regulator...38 Safeguard...39 SQL/MX Release J CLIM Fallback Considerations for Multiple Providers per CLIM Contents

5 Gen8 CLIMs...39 Halt and Hard Reset Processors When Upgrading to J NonStop Server for Java NonStop SOAP NonStop Software Essentials Safeguard...40 SQL/MX Release Upgrade Checklist...41 Required Information Checklists...41 Upgrade Checklist Preparing to Upgrade the Server Software (Preinstallation Tasks)...46 Back Up Important Files...46 Back Up NonStop SQL/MP...46 Back Up NonStop SQL/MX files...46 Back Up Spooler Control files...46 Back Up TMF Files...46 Back Up CLIM Configuration Files...46 Record the Current SYSnn...47 Save the Current Configuration File (CONFxxyy)...47 Verify System Processes...48 Check Processor Status...48 Check System Components...48 Verify the State of the Internal ServerNet Fabric...50 Verify Firmware...50 Verify Critical System Processes...50 Verify Disk Drives...52 Verify Tape Drives (If Necessary)...52 Verify That the CLIMs Are in the Started State...53 Verify That the CIP Providers Are in the Started State...53 Check the Status of the Spooler Collector...53 Check for Sufficient Swap File Space...53 Install Node Interoperability SPRs...54 Back Up System Information...56 For NonStop BladeSystems NB54000c, NB54000c-cg, NB56000c, and NB56000c-cg, Ensure the Core License File is Ready for Migration...56 If Necessary, Manually Install the NonStop Software Essentials Server Product Installing a SUT for This RVU Using NonStop Software Essentials...58 Alerts for Installing a SUT...58 Back Up Important Files...58 Receive New Software Into the Archive...58 Create a New Software Revision...61 Build and Apply the New Software Revision...64 Print Operator Instructions From the Target Interface (ZPHITI)...66 Recovery for Problems Installing This RVU SUT or SPRs...69 Cancel Pending Build/Apply Requests Installing a SUT for This RVU Using the Planner Interface...70 Alerts for Installing a SUT...70 Back Up Important Files...70 Receive New Software Into the Archive...70 Create a New Software Revision...74 Build and Apply the New Software Revision...77 Print Operator Instructions From the Target Interface (ZPHITI)...82 Recovery for Problems Installing This RVU SUT or SPRs...85 Contents 5

6 Cancel Pending Build/Apply Requests Running ZPHIRNM...86 Alerts...86 Back Up (Copy) Files in the $SYSTEM.ZTCPIP Subvolume (Best Practice)...86 Stop Applications...87 Drain the Spooler (Optional)...87 Back Up the Spooler Control Files...88 ZPHIRNM...88 Using ZPHIRNM PREVIEW Mode...88 Steps for Running ZPHIRNM...89 Verify That ZPHIRNM Ran Successfully Loading This RVU...91 Alerts...93 Perform Updates Before Halting the Processors...93 Perform Required RVU-Specific Upgrades...93 When Upgrading From J06.04 or an Earlier RVU: Removing #ZPLS...93 When Upgrading From J06.05 or an Earlier J-Series RVU: CLIM Software...94 If You Are Migrating to a Another NonStop System...94 Determine If the System Firmware Version Will Need to Be Upgraded...94 Determine If the HSS Firmware Version Will Need to Be Upgraded Halt the Processors (Conditional): Update the System Firmware (Conditional): Update the HSS Firmware...96 Updating the HSS Firmware on All J-Series Systems Except NS2000 Series...96 Updating HSS Firmware on NS2000 Series System Blade Elements (Required Only for Upgrade from J06.13 or Earlier to J06.14 or Later) Perform a Hard Reset Upgrade the CLIM Software (Optional) Update the CLIM Firmware Loading the System...98 Steps for Loading the System...98 Completing the System Load (If Necessary) Verifying That the System Is Started Updating Firmware (If Necessary) After the System Load Resuming Normal Operations Revive the Down Half of the Mirrored Disk Your Core License Start System Applications Before Starting DSM/SCM Initialize SQL for NonStop SQL/MP Cold Start the Pathway Configuration Start DSM/SCM Run merge_whatis Configure Specific Products (Post-System Load) Update NonStop TCP/IP Configuration Files Step 1: Copy the Sample TCP/IP Files Into $SYSTEM.ZTCPIP (Optional) Step 2: Check the PROTOCOL File (Optional) Step 3: Optional: For Planner Interface, Ensure That PORTCONF and SERVICES Files Are Complete Configure OSS Install Specific OSS Files Using COPYOSS or PINSTALL Contents

7 Run the inetd Process Using OSS Unautomated Configuration and Startup Using OSS EasySetup (T0585) Configure SMF (Optional) Configure the Remote Database Facility Configure the WAN Manager Set Up itp WebServer Re-deploy NonStop SOAP Backing Out the DSM/SCM Revision Products That Might Have Fallback Implications Open System Services Storage Management Foundation Before Backing Out the Revision Start the Target Interface (ZPHITI) Submit a Backout Request Monitor the Backout Process Using NonStop Software Essentials Monitor the Backout Process Using the Planner Interface Running ZPHIRNM to Reactivate the Previous Software Revision Fallback Considerations for NonStop Software Essentials After ZPHIRNM Alerts Drain the Spooler (Optional) Run ZPHIRNM Using PREVIEW Mode Run ZPHIRNM Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations Fallback Considerations for the Power Regulator Alerts Task Overview Before Halting the Processors If Falling Back to J06.14 or an Earlier RVU (Optional) Prepare to Fall Back to Previous CLIM Firmware Prepare to Fall Back to Previous CLIM Software When Falling Back to the J06.04 or Earlier RVU Modify OSSINFIL If Using CLIMs for BOOTP, DHCP, or DNS Services Halt the Processors While the Processors Are Halted (Optional) Fall Back to Previous CLIM Firmware Reimage the CLIMs Prepare the CLIMs Load the System Complete the System Load (If Necessary) Using the SSOCLIM * Option to Run SSOCLIM on All Available CLIMs Complete CLIM Setup Revert Firmware (If Necessary) Install Specific OSS Files (If Necessary) Verify That the System Is Started A Using DSM/SCM With NonStop Software Essentials to Install SPRs Tools for Managing SPRs Scout for NonStop Servers DSM/SCM SPRNOTES Contents 7

8 Install SPRs Using DSM/SCM With NonStop Software Essentials Save the Current Configuration Determine the Current SYSnn Receive the SPR Into the DSM/SCM Archive Before Starting DSM/SCM Bring the SPR Into the DSM/SCM Archive Create a New Software Configuration That Includes the SPR Build the New Revision Print Operator Instructions From the Target Interface (ZPHITI) Run ZPHIRNM If Running INSTALL^TEMPLATES Is Required If a System Load Is Required Halt the Processors Perform a System Load Start Your Applications and Processes B Using DSM/SCM With the Planner Interface to Install SPRs Tools for Managing SPRs Scout for NonStop Servers DSM/SCM SPRNOTES Install SPRs Using DSM/SCM With the Planner Interface Save the Current Configuration Determine the Current SYSnn Receive the SPR Into the DSM/SCM Archive Before Starting DSM/SCM Bring the SPR Into the DSM/SCM Archive Create a New Software Configuration That Includes the SPR Build the New Revision Print Operator Instructions From the Target Interface (ZPHITI) Run ZPHIRNM If Running INSTALL^TEMPLATES Is Required If a System Load Is Required Halt the Processors Perform a System Load Start Your Applications and Processes C Copying the DSM/SCM, NonStop Software Essentials, and SWID SPRs from the SUT Using NonStop Software Essentials Alerts Determine the Product Version of NonStop Software Essentials Server on the Host System and the SUT Determine the Product Version of DSM/SCM on the Host System and the SUT Determine the SWID Product Version on the Host System and the SUT Copy (RESTORE) the DSM/SCM Server, NonStop Software Essentials Server, and SWID Product Versions from the SUT to Disk Receive the H02 DSM/SCM, NonStop Software Essentials Server, and SWID SPRs Create a New Software Revision for H02 DSM/SCM, NonStop Software Essentials, and SWID SPRs Build and Apply the DSM/SCM H02 Software Product Revision Run the INSTALL^TEMPLATES Macro If Migrating to J06.12 or an Earlier RVU, Install the Latest NonStop Software Essentials Server SPR Using Scout Restart Applications Before Starting DSM/SCM Start DSM/SCM Contents

9 Verify that the SUT Version of DSM/SCM is Installed Verify that the SUT or Scout Version of the NonStop Software Essentials Server is Installed Verify that the SUT Version of SWID Is Installed Recovery for Problems While Installing the H02 Version of DSM/SCM If NonStop Errors Are Displayed Cancel Pending Build/Apply Requests Install the Latest Version of the NonStop Software Essentials Client D Copying the DSM/SCM and SWID SPRs from the SUT Using the Planner Interface Alerts Determine the Product Version of DSM/SCM on the Host System and SUT Determine the SWID Product Version on the Host System and SUT Determine the Product Version of DSM/SCM on the Client Copy (RESTORE) the H02 DSM/SCM Product Version to Disk (If Necessary) Receive the H02 SWID and DSM/SCM SPRs Create a New Software Revision for H02 DSM/SCM and SWID SPRs Build and Apply the DSM/SCM H02 Software Product Revision Rename the Applied DSM/SCM H02 Files By Running ZPHIRNM Run the INSTALL^TEMPLATES Macro Restart Applications Before Starting DSM/SCM Start DSM/SCM Verify That the Correct SPR for DSM/SCM is Installed Verify That SWID Is Installed Recovery for Problems While Installing the H02 Version of DSM/SCM If NonStop Errors Are Displayed Cancel Pending Build/Apply Requests Install the DSM/SCM Client From ZDSMSCM Determine Your DSM/SCM Client Software Version Determine the Current IP Address and Port Number Copy the ZDSMSCM Client File From the Host Install the DSM/SCM Client Software E Updating SWAN Concentrator CLIP Firmware Acronyms Index Contents 9

10 Tables 1 Tasks and Tools for Backing Out to the Previous SYSnn Maintenance Entity (ME) Firmware File Names and Locations Maintenance Entity (ME) FPGA File Names and Locations Server Blade Firmware for All NonStop System Running J-Series Software Except for the NS2000 Series System Blade Element Firmware for NonStop NS2000 Series Systems ServerNet Adapters Used With J-Series NonStop Systems J-Series ServerNet Adapters Firmware Information Updateable Firmware for the NonStop ServerNet 6770 and 6780 Cluster Switch File Names and Locations Updateable Firmware for S-series Interoperability NonStop SQL/MX and Supported RDF Versions Required Information Checklist, Before You Start Information to Gather During the Upgrade (Checklist) Upgrade Checklist Interoperability SPRs for G-Series RVU Systems Connected Through Expand to H-Series or J-Series RVU Systems Interoperability SPRs for H-Series RVU Systems Connected through ServerNet to J-Series RVU Systems Interoperability SPRs for G-Series RVU Systems Connected through ServerNet to J-Series RVU Systems Interoperability SPRs for G-Series RVU Systems Connected through ServerNet to H-Series RVU Systems SPRs for Software Migration and Software Management Operations Between G-Series, H-Series and J-Series RVU-Based Systems System Load Paths in Order of Use for FCDM-Load System Load Paths in Order of Use for CLIM-Attached-Load...91

11 About This Document This guide describes: Upgrading the initial J06.15 RVU through the use of SUT refreshes, if necessary. Falling back to a previous SYSnn. Supported RVUs This manual supports the J RVU and all subsequent J06.15 RVUs unless otherwise noted. Intended Audience This guide is written for operations staff and support personnel and requires a working knowledge of Windows Server 2003, Windows Server 2008, Windows Server 2012, OSM client and server components, system console software, NonStop Software Essentials, DSM/SCM, Target Interface (ZPHITI), and ZPHIRNM applications. New and Changed Information in This Edition This 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, see the H06.nn Software Installation and Upgrade Guide. System migration planning. System-wide issues involved in migrating to the latest J-series RVU are 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 target system using an Expand connection or tape. See the NonStop Software Essentials User's Guide or 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 HP and third-party system console client software, such as OSM client-based components, see the NonStop System Console Installer Guide. Installing and configuring OSM server components. To install and configure OSM server components, and start using client-based components, see the OSM Configuration Guide. Installing, configuring, and migrating to HP NonStop SQL/MX. The SQL/MX Installation and Management Guide provides step-by-step instructions for installing and configuring NonStop SQL/MX. Migrating a G-series NonStop SQL/MX or NonStop SQL/MP database to a J-series RVU and falling the database back to G-series RVUs is the same as for migrating to an H-series RVU. For information about migrating a G-series database, see the SQL Supplement for H-Series RVUs. Installing and configuring NonStop systems and hardware components. Contact your HP authorized service provider. Supported RVUs 11

12 Notation Conventions General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH Italic Letters Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed in brackets are required. 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 example if (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?123 CODE RECEIVED: The user must press the Return key after typing the input. Related Information NOTE: Many of the documents referenced in this guide are located in the NTL, which has moved to the HP Business Support Center (BSC) at The CLuster I/O Module (CLIM) Software Compatibility Reference provides the compatibility information 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 OSM client-based components, and other applications on system consoles. The J06.nn Release Version Update Compendium for this RVU provides summary information on the new features and migration issues. The comforte MR-Win6530 online help provides information on configuring MR-Win6530 sessions. 12

13 The Support and Service library and guided procedures provide online help and web-based instructions for performing many tasks, including updating firmware. The Support and Service library is available in the NonStop Technical Library (NTL). The NonStop Software Essentials User's Guide provides detailed, task-oriented instructions for using NonStop Software Essentials. The DSM/SCM User's Guide provides detailed, task-oriented instructions for using DSM/SCM to perform the various tasks associated with installing and managing software revisions. For information about planning and configuring the installation of NonStop systems, see the planning guide for your system. The NonStop Operations Guide provides information for operating and maintaining the NonStop BladeSystem server. For detailed instructions and checklists for installing a NonStop system, see the hardware installation manual for your system. The OSM Configuration Guide provides an overview of all OSM applications and components, how to configure and get started with OSM, and how to use the primary OSM interface, OSM Service Connection, to monitor and perform actions on system and cluster resources. Publishing History Part Number Product Version N.A. Publication Date February 2013 HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to [email protected]. Include the document title, part number, and any comment, error found, or suggestion for improvement you have concerning this document. Publishing History 13

14 1 Overview of Installing This RVU For information on installing SPRs, see Using DSM/SCM With NonStop Software Essentials to Install SPRs (page 133) or Using DSM/SCM With the Planner Interface to Install SPRs (page 140). SUT on DVD The J-series SUT is also available on DVD. For instructions on installing the SUT from the DVD, see the IPSetup User s Guide. WARNING! See the Support Note S12017 (IPSetup on 64-bit Windows causes IE problems) for information about preventing or recovering from an Internet Explorer issue that can occur on 64-bit Windows operating systems. CLIM Software for This RVU If your system has CLIMs installed, the CLIM software is available on a separate DVD and in Scout for NonStop Servers. Before installing CLIM software on your NonStop system, you must install the software on the system console as described in the Cluster I/O Protocols (CIP) Configuration and Management Manual. CLIM software compatibility across RVUs is documented in the CLuster I/O Module (CLIM) Software Compatibility Reference. Disk Space Requirements The 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 RVUs There are no known operational differences between H-series and J-series RVUs. Operational differences between G-series and J-series RVUs are the same as for G-series and H-series; for that information, see the H06.nn Software Installation and Upgrade Guide. Investigating a J-Series RVU Several 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 and features for each J-series RVU. It also discusses the effect these changes have on installation and configuration, operations and management, data files, applications, and networks. The IUG2 simplifies the planning of software and hardware for J-series RVUs. Select the products and RVUs you use, and the Interactive Upgrade Guide 2 automatically displays customized migration instructions and lists new features. The Managing Software Changes manual explains TRM2000 and provides information about system migration and installation processes, SPR analysis, and resources for investigating new RVUs and SPRs. Scout for NonStop Servers is a Web-based SPR analysis and delivery tool. You can access Scout through HP NonStop eservices Portal at: 14 Overview of Installing This RVU

15 Online help for using Scout is available on the Scout Web site. Scout or the DSM/SCM Planner Interface can be used to view and print softdocs and release documents on the SUT after you receive new software into the archive. For more information, see the DSM/SCM User's Guide or Scout. NonStop System Console Requirements A NonStop system console (NSC) is an HP-supplied personal computer used to run OSM and other maintenance and diagnostic software for NonStop servers. For information on currently supported hardware models and other requirements, as well as the latest available console software, see the NonStop System Console Installer Guide. IMPORTANT: HP requires that you connect two consoles configured as a primary and backup pair to a system. Console Requirements for Dedicated Service LANs When a dedicated service LAN is present, make sure that: Only one pair of consoles (primary and backup) serves the entire dedicated service LAN (all other consoles in LAN systems must be powered OFF). Also make sure that this console pair meets these requirements when connected to a LAN also being used to manage one or more NonStop X NS7 systems. Both consoles must be running Windows Server 2008 or Windows Server 2012 and have the latest software installed from the NonStop System Console Installer DVD Update 23 (or later). For more information, ask your authorized service provider to refer to the NonStop Dedicated Service LAN Installation and Configuration Guide for the NonStop System. Updating System Consoles (Optional) IMPORTANT: HP recommends that you always update the software on a console pair, including the OSM Console Tools, to the versions provided on the latest NonStop System Console Installer DVD. NonStop System Console Installer DVD Update 24 (or later) contains important hotfixes for using OSM server software for consoles running Windows Server 2012, and also for HP SIM 7.2. NonStop Software Essentials and Console Requirements NOTE: HP recommends installing HP SIM and NonStop Software Essentials on a separate Central Management Server (CMS), but supports installing these products on the NonStop system console as well. Either way, the products can be installed or upgraded from the HP Insight Control for NonStop DVD that ships with the NSC DVD. For more information on whether installing HP SIM and NonStop Software Essentials on the system console or a separate CMS makes sense for your LAN environment, see HP SIM for NonStop Manageability, located in the NonStop Technical Library (NTL). This guide shows you how to upgrade the RVU using either NonStop Software Essentials, an HP SIM plug-in, or the DSM/SCM Planner Interface. If you are using a 64-bit console, you must use NonStop Software Essentials, as the DSM/SCM client and its Planner Interface are not supported on 64-bit consoles. If not already installed, both HP SIM and the NonStop Software Essentials client component can be installed from the HP Insight Control for NonStop DVD that ships with the NonStop System Console Installer DVD (Update 17 or later). You can also download HP SIM and the NonStop Software Essentials client component from Scout, and download HP SIM from For more information on installing and getting started with NonStop NonStop System Console Requirements 15

16 nl Software Essentials server and client components, see the NonStop Software Essentials Installation and Quick Start Guide. Software Product NonStop Software Essentials Server NonStop Software Essentials Client (Windows) NonStop Software Essentials Client (Linux) T-Number T0894 T0895 T0996 NOTE: NonStop Software Essentials requires that a server component be installed on the NonStop system. That server component is on the SUT for J06.13 and later, but can also be downloaded from Scout. If the NonStop Software Essentials server component is not installed on your NonStop systems, see the Nonstop Software Essentials Installation and Quick Start Guide. Using OSM With This RVU HP recommends that you the latest versions of the OSM server and client software, along with other console software. OSM Server-Based Component The server-based OSM SPR released with this RVU is T0682H02^ADD. This version may be superseded by a later version. For more information about this server version, see the J06.15 Release Version Update Compendium or the OSM Service Connection User s Guide, which is also available as online help with the OSM Service Connection. For detailed information about the OSM server-based component, including configuration options, see the OSM Configuration Guide. OSM Client-Based Components The OSM client-based products, which can be upgraded from the NSC Installer DVD, include: OSM Low-Level Link (T0633), which is used primarily for down-system support, allowing you to communicate with your HP NonStop server even when the NonStop Kernel operating system is not running. In addition to performing the system loads, it is used to configure VIO and other modules, configure CLIMs, and update CLIM software, and copy/update HSS files for J-series. For information about other features and functionality, see the OSM Configuration Guide and the OSM Low-Level Link online help. OSM Console Tools (T0634), which includes: OSM System Inventory Tool OSM Certificate Tool (for Onboard Administrators) CLIM Management Tool NonStop Maintenance LAN DHCP DNS Configuration Wizard OSM Quick Start Tool Apache OpenOffice 16 Overview of Installing This RVU

17 Using DSM/SCM and NonStop Software Essentials With This RVU NonStop Software Essentials and This RVU The HP NonStop Software Essentials product is a software installation and management tool for NonStop servers. NonStop Software Essentials uses DSM/SCM server software and provides a replacement for DSM/SCM Planner Interface functions as well as certain Host Maintenance Interface functions that is more secure, easier to use, and overcomes other shortcomings of DSM/SCM. It coexists with DSM/SCM; you can use either NonStop Software Essentials or the DSM/SCM Planner Interface for tasks in which there is overlapping functionality. For more information, see the NonStop Software Essentials Installation and Quick Start Guide and the NonStop Software Essentials User's Guide. These rules apply: You should install the latest NonStop Software Essentials server (T0894) and client (T0895) components available to take advantage of the latest enhancements. Copying the DSM/SCM, NonStop Software Essentials, and SWID SPRs from the SUT Using NonStop Software Essentials (page 147) and Copying the DSM/SCM and SWID SPRs from the SUT Using the Planner Interface (page 156) describe the two options for installing the latest NonStop Software Essentials server SPR, depending on whether you have NonStop Software Essentials running or must use the DSM/SCM Planner Interface. NonStop Software Essentials 4.0 client can be installed from the HP Insight Control for NonStop DVD that ships with HP NonStop System Console Installer DVD, Update 23 or later. While it can be used with NonStop Software Essentials server version 2.0 and later, server version 4.0 is required to take advantage of the new functionality provided in release 4.0. When used with earlier NonStop Software Essentials server versions (2.0 and later), you will receive Limited Functionality warnings when performing some operations. You can proceed with those operations despite those warnings. NonStop Software Essentials 1.0 server and client components are not compatible with subsequent NonStop Software Essentials server and client components (2.0 and later). NonStop Software Essentials was first released on SUT in J06.13 and is available by SPRs for RVUs J06.03 through J NonStop Software Essentials components are backwards compatible and it is recommended that you get the latest server and client components available regardless of your RVU level. For more information, see the NonStop Software Essentials Installation and Quick Start Guide. You cannot use the DSM/SCM Planner Interface on systems with 64-bit NonStop system consoles. If you have a 64-bit NonStop system console but do not have the NonStop Software Essentials server installed on your system, your options are: Use the DSM/SCM Planner Interface from an older (32-bit) console to install NonStop Software Essentials server; or Manually install the server as described in the NonStop Software Essentials Installation and Quick Start Guide. In either case, once compatible NonStop Software Essentials server and client components are installed, you can use NonStop Software Essentials to perform RVU upgrades and all other NonStop software management functions formerly performed through the DSM/SCM Planner Interface. Using DSM/SCM and NonStop Software Essentials With This RVU 17

18 DSM/SCM and This RVU OSBUILD SPR CAUTION: Before you install the SUT, you must copy the SUT version of the DSM/SCM server to your host system. When you copy the DSM/SCM server SPR, you must also upgrade the SWID product (T9298H02) at the same time to avoid a fingerprint or mismatched file problem. If you are upgrading DSM/SCM paired with NonStop Software Essentials, see Copying the DSM/SCM, NonStop Software Essentials, and SWID SPRs from the SUT Using NonStop Software Essentials (page 147) for the detailed instructions. If you are upgrading DSM/SCM paired with the Planner Interface, see Copying the DSM/SCM and SWID SPRs from the SUT Using the Planner Interface (page 156) for the detailed instructions. Also be aware of the following: A new type of hardware platform and selectable option, TNS/E, has been added to the Planner 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 is configured 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. WARNING! If a J06.03 or later host system is used to perform DSM/SCM builds for a target system 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 the DSM/SCM Sysgen (OSBUILD) will fail. The build will complete successfully if it is being done for an H06.12 or later system. The appropriate T0431 SPRs are: SPR T0431H01^AAK T0431H01^AAH T0431H01^AAN T0431H01^AAM T0431H01^AAL Target NonStop System RVU H06.10 and H06.11 H06.09 H06.08 H06.07 H06.05 and H06.06 Any J-series RVU attempting to build an H-series RVU prior to H06.12 must install these SPRs. DSM/SCM and Public DLLs DSM/SCM manages and controls the distribution, installation, and activation of public DLLs in J-series RVUs the same way as H-series RVUs. Public DLLs are installed on the J-series and H-series target systems in their own subvolume. DSM/SCM and OSS When performing a Build/Apply, ensure that the setting of the Manage OSS Files option matches your target system. If the target system is not to use OSS, you must uncheck the OSS files option box before beginning a Build request. If the box is left checked, OSS is included by the Build request. The OSS root fileset needs to be configured and started before files can be copied into the OSS file system by DSM/SCM. For OSS users who request HP to install OSS, it is assumed 18 Overview of Installing This RVU

19 that OSS is installed and configured. However, the OSS root fileset ($ZPNS) must be in the started state; otherwise, the Build/Apply fails. Upgrading the NonStop Software Essentials Client You can upgrade your NonStop Software Essentials client from the HP Insight Control for NonStop DVD that ships with the NonStop System Console Installer DVD. The HP Insight Control for NonStop DVD also contains the installer for HP SIM. For more information, see the NonStop System Console Installer Guide. You can also download the NonStop Software Essentials client component from Scout, and download HP SIM from: Software Product NonStop Software Essentials Server NonStop Software Essentials Client (Windows) NonStop Software Essentials Client (Linux) T-Number T0894 T0895 T0996 For instructions on installing NonStop Software Essentials, see the NonStop Software Essentials Installation and Quick Start Guide. Upgrading the DSM/SCM Client (Planner Interface) and the T6031H02 PVU To upgrade the DSM/SCM client, if using 32-bit consoles on which it is supported, follow the client or Planner Interface you did not order new system consoles, the DSM/SCM client version must be downloaded from the ZDSMSCM subvolume. (If you have acquired new system consoles, 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 the DSM/SCM client or Planner Interface installation instructions in the DSM/SCM User s Guide or Copying the DSM/SCM, NonStop Software Essentials, and SWID SPRs from the SUT Using NonStop Software Essentials (page 147). Summary of Software Installation Tasks To install software using DSM/SCM, perform these tasks: 1. Receive new software into the DSM/SCM Archive. When software is received, the files from each product are stored in the DSM/SCM Archive, a holding area for your software. File attributes are stored in the DSM/SCM host database. 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 into a 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 that are 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 new software revision. During the Apply process, the activation package is transferred to the target system, and the new software is placed on the target system s subvolumes. When the Apply Using DSM/SCM and NonStop Software Essentials With This RVU 19

20 request is finished, a snapshot is automatically created and returned to the host, if Expand-connected. 4. Activate the new operating system image. During the Build/Apply phase, DSM/SCM places product files in their TSVs with temporary (fabricated) file names so that the new files do not conflict with the file names of currently running programs. You run the ZPHIRNM program on the target system to: Rename the files that currently have actual file names to fabricated names. These files become 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 ZMODGP if 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 (as compared to the last configuration activated). If no ZcccGP files change, ZMODGP is not run. ZMODGP is a TACL script that makes changes to the generic-process definitions in the system configuration database. When you use the ZMODGP script, you do not need 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 SUBSYS command. The CONFTEXT file directive TAPE_LABEL_PROCESSING gets overridden by the Storage Subsystem settings. See the SCF Reference Manual for the Storage Subsystem for more information about the ALTER SUBSYS command. The processor type (SYSTEM_PROCESSOR_TYPE) is specified in the CONFTEXT file. It currently has only one value: System NB50000c, NB50000c-cg, NB54000c, NB54000c-cg, NS2200 series, NS2100, and NS2000 series SYSTEM_PROCESSOR_TYPE NSE-M Check the CONFTEXT file to ensure that the following entries are present. They are needed for the implicit DLLs: SYSTEM_IMPLICIT_INIT_FILES SYSTEM_IMPLICIT_CORE_FILES SYSTEM_IMPLICIT_FS_FILES SYSTEM_IMPLICIT_MCP_FILES SYSTEM_IMPLICIT_ETC_FILES This example shows a CONFTEXT file: $TEMP CONFIGXX 2> type conftext ALLPROCESSORS: SYSTEM_PROCESSOR_TYPE SYSTEM_VOLUME_SUBVOL SYSTEM_LIBRARY_CODE_FILES SYSTEM_PROCESS_CODE_FILES SYSTEM_PROCESS_LIBRARY_FILES TANDEM^IMPLICIT^INIT^FILES; TANDEM^IMPLICIT^CORE^FILES; TANDEM^IMPLICIT^FS^FILES; TANDEM^IMPLICIT^MCP^FILES; TANDEM^IMPLICIT^ETC^FILES; NSE-M; $SYSTEM.SYS00; TANDEM^LIBRARY^CODE^FILES; TANDEM^PROCESS^CODE^FILES; TANDEM^PROCESS^LIBRARY^FILES; 20 Overview of Installing This RVU

21 STANDARD_MICROCODE MICROCODE_FILES FILES_TO_COPY_TO_NEW_SYSTEM SYSTEM_IMPLICIT_INIT_FILES SYSTEM_IMPLICIT_CORE_FILES SYSTEM_IMPLICIT_FS_FILES SYSTEM_IMPLICIT_MCP_FILES SYSTEM_IMPLICIT_ETC_FILES FORMATTER_TEMPLATE_FILES INITIAL_COMINT_INFILE Installing CLIM Software TANDEM^STANDARD^MICROCODE; TANDEM^MICROCODE^FILES; TANDEM^FILES^TO^COPY; TANDEM^IMPLICIT^INIT^FILES; TANDEM^IMPLICIT^CORE^FILES; TANDEM^IMPLICIT^FS^FILES; TANDEM^IMPLICIT^MCP^FILES; TANDEM^IMPLICIT^ETC^FILES; TANDEM^FORMATTER^TEMPLATE^FILES; $DSMSCM.SYS.CIIN; If your NonStop system has CLIMs installed, you must upgrade the CLIM software prior to cold loading the SUT. The procedure for upgrading CLIM software is described in the Cluster I/O Protocols (CIP) Configuration and Management Manual. Backing Out the DSM/SCM Revision If you encounter a problem with a SUT refresh that cannot be resolved, you can back out the DSM/SCM revision. Table 1 Tasks and Tools for Backing Out to the Previous SYSnn To Perform This Task Submit a backout request. 2. Reactivate the previous software revision. 3. Load the HP NonStop operating system and, if CLIMs are installed, load the CLIM software from the previous revision into the first processor. 4. Reload the remaining processors. Use This Tool... DSM/SCM Target Interface (ZPHITI) DSM/SCM ZPHIRNM program OSM Low-Level Link TACL RELOAD command Documented in This Chapter... Backing Out the DSM/SCM Revision (page 21) Chapter 12: Running ZPHIRNM to Reactivate the Previous Software Revision Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations (page 119) Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations (page 119) Managing Microcode and Firmware When you install a new RVU, you must ensure you are running the current firmware and microcode versions and upgrade those products, if necessary. The current firmware versions and upgrade procedures are given in Chapter 2: Managing Microcode and Firmware Installation, Migration, and Fallback Many products have special considerations for installation, migration, and fallback, which you should be aware of before installing the new RVU. These considerations are described in Chapter 3: Installation, Migration, and Fallback Considerations for This RVU. Perform an RVU Upgrade on a Node For instructions on how to perform an RVU upgrade on a node connected to any ServerNet Cluster topology (such as a BladeCluster Solution, ServerNet Cluster 6770, ServerNet Cluster 6780, or a combination of these topologies), see the procedure in the NonStop BladeCluster Solution Manual. Installing CLIM Software 21

22 2 Managing Microcode and Firmware NOTE: Trained HP authorized service providers will update the firmware when they install any FRUs. Firmware, unless otherwise noted, is considered customer-updateable. You must manage all microcode and firmware within your system properly, ensuring compatible versions are installed. Failure to do so can result in a wide range of system problems, from intermittent faults to partial or complete system outages. Carefully review the NonStop Firmware Matrices document, located in the Service Information section of the Support and Service collection of the NonStop Technical Library at 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, you can use the FILEINFO command to see firmware files. Enter this FILEINFO command, if your Carrier Grade system is connected to a NonStop S-series server, 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 other firmware, such as ServerNet Clustering: $SYSTEM STARTUP 7> FILEINFO $SYSTEM.SYS??.M???? Managing BladeCluster Software and Firmware Requirements The software and firmware required for the BladeCluster Solution is included in this RVU. For more information, see the BladeCluster Solution Manual. Managing ME Firmware and ME FPGA Firmware There is ME firmware and ME FPGA firmware on the ServerNet switches located in c7000 enclosures, 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. ME firmware and ME FPGA can be checked and, if necessary, updated from either the OSM Service connection or the Low-Level Link. For systems with VIO and G16SE enclosures, all enclosures in a system should have consistent versions. ME firmware and ME FPGA can be checked and, if necessary, updated from either the OSM Service connection or the Low-Level Link. For information on using OSM Low-Level Link to perform ME firmware updates, see the online help available within the application. If you have legacy NonStop S-series enclosures attached to your system, you will also have SP firmware to check. For more information on updating SP firmware, see the current G06.nn Software Installation and Upgrade Guide. Updating ME Firmware NOTE: For product levels, see the NonStop Firmware Matrices document. 22 Managing Microcode and Firmware

23 Table 2 Maintenance Entity (ME) Firmware File Names and Locations Firmware Name Component File Name Default Location ME firmware (see Caution below) ServerNet Switch (IOAM enclosure) M2805 SYSnn subvolume Blade ME firmware (see Caution below) ServerNet Switch (c7000 enclosure) M4805 SYSnn subvolume ME firmware for IME in G16SE and VIO enclosures (see Caution below) VIO enclosure logic board M1805 SYSnn subvolume For more information on managing ME firmware, see: The planning guide or hardware installation manual for your system. The online help in the OSM Low-Level Link or OSM 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 NonStop BladeSystems. 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 Enclosure There is maintenance entity (ME) firmware on the ServerNet Switches within the c7000 enclosures of 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 and You can select either switch. 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 and ) Updating ME Firmware on a VIO Enclosure and G16SE Enclosure There is ME firmware on the VIO Logic Board object in each VIO enclosure. Managing ME Firmware and ME FPGA Firmware 23

24 NOTE: In the OSM Low-Level Link, a G16SE enclosure is shown as a VIO module. In the OSM Low-Level Link, a VIO or G16SE logic board is represented as an IME object. To use the OSM Service Connection to update the ME firmware for VIO and G16SE enclosures: 1. Locate the VIO Logic Board: in the tree pane, select one of, depending on the type of server: System > Fabric Group > Internal ServerNet Fabric > VIO Module > VIO Logic Board. or System > Group nnn > VIO Module > VIO Logic Board 2. 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 or G16SE enclosure in the other fabric. Updating ME FPGA NOTE: For firmware levels, see the NonStop Firmware Matrices document, located in the Service Information section of the Support and Service collection of the NonStop Technical Library at Table 3 Maintenance Entity (ME) FPGA File Names and Locations Firmware Name Component File Name Default Location ME FPGA (see Caution below) ServerNet Switch (c7000 enclosure) SAM0815 SYSnn ME FPGA (see Caution below) ServerNet Switch (IOAM enclosure) SAM0437 SYSnn ME FPGA for IME in G16SE enclosures and VIO enclosures (see Caution below) VIO enclosure logic board SAM0789 SYSnn 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 c7000, G16SE, and VIO enclosures and IOAMs just as you did when updating ME firmware, but choose the ME FPGA Update action instead. For information on using the OSM Low-Level Link to update ME FPGA, see the online help available within the application. Managing OA Firmware for the c7000 Enclosure Check the NonStop Firmware Matrices document for the minimum supported OA firmware for this release. Managing Server Blade Firmware and Blade Element Firmware NOTE: For minimum firmware levels for this RVU, see the NonStop Firmware Matrices document. 24 Managing Microcode and Firmware

25 Table 4 Server Blade Firmware for All NonStop System Running J-Series Software Except for the NS2000 Series System Firmware Name Halted State Services firmware ISP1040 firmware DISKBOOT firmware Product Description Used to reset, halt, load, and dump a server blade. Delivered as an Independent Product on the NSC DVD. Controller firmware for legacy I/O or SCSI disks in G-series RVUs. Used during a system load. Table 5 Blade Element Firmware for NonStop NS2000 Series Systems Firmware Name Halted State Services and HPI Loader T8004 Firmware Product Description Used to reset, halt, load, and dump a blade element. Delivered as an Independent Product on the NSC DVD. ISP1040 Firmware DISKBOOT Firmware Controller firmware for legacy I/O or SCSI disks in G-series RVUs. This firmware is packaged as part of the DVD containing T8004 and cannot be updated independently. Used during a system load. This firmware is packaged as part of the DVD containing T8004 and cannot be updated independently. The installation procedure for blade element firmware is described in the Updating Blade Element Firmware in an NS2200 Series, NS2100, NS2000 Series, NS1200 or NS1000 Server service procedure. Managing ServerNet Adapter Firmware Table 6 (page 25) identifies the ServerNet adapters that can be installed in or connected to J-series NonStop systems. Table 6 ServerNet Adapters Used With J-Series NonStop Systems ServerNet Adapter Fibre Channel ServerNet Adapter (FCSA) Gigabit Ethernet 4-port ServerNet Adapter (G4SA) 6763 Common Communication ServerNet Adapter (CCSA) Token Ring ServerNet Adapter (TRSA) Where Adapter Is Installed IOAM enclosure in a NonStop BladeSystem IOAM enclosure in a NonStop BladeSystem I/O enclosure in a NonStop S-series system connected to ServerNet switches in a NonStop BladeSystem c7000 enclosure I/O enclosure in a NonStop S-series system connected to ServerNet switches in a NonStop BladeSystem c7000 enclosure To determine if the firmware for an installed FCSA, GS4A, or CCSA adapter needs to be updated, navigate down the OSM tree pane for FCSA, G4SA, or CCSA: CAUTION: Ensure that the system is running the new RVU before starting this procedure. Managing ServerNet Adapter Firmware 25

26 For detailed information on updating FCSA, G4SA, and CCSA firmware using the OSM Service Connection, see the OSM online help on the OSM Multi-Resource Action dialog box. FCSA. The FCSA has two ports that allow connection to external fibre-channel-enabled devices. The firmware files are pre-installed on the FCSAs in a new NonStop BladeSystem. You might need to update these firmware files using either OSM or SCF. The flash boot firmware (T0630G06) contains version information about the boot firmware located in the FCSA FLASH memory. The boot firmware runs on every FCSA after power on and after hardware or firmware errors, and is re-downloaded to initialize the adapter and to accept downloaded firmware from the processor. The AAN SPR is available for this T number. The flash firmware (T0612G06) contains version information about the operational firmware located in the FCSA FLASH memory. Flash firmware runs the FCSAs used for system 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 the first 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 the firmware, using the FCSA firmware objects and actions described in the OSM Service Connection User s Guide. If the Compare State shows Down-rev, update the firmware. The following example shows that the firmware is at an earlier version and needs to be updated: 26 Managing Microcode and Firmware

27 G4SA. G4SAs can only be installed in an IOAM. Firmware is pre-installed on G4SAs in a new NonStop BladeSystem. You might need to update the firmware using either OSM or SCF. Use the OSM Service Connection to display G4SA firmware attributes and action under the G4SA SAC object. To check or update G4SA firmware using the OSM Service Connection, locate and expand the G4SA, then select its subcomponent G4SA SAC object. In the following example, the firmware attributes show that the current firmware Version is the same as the available Default File Version; no update is necessary. If the Compare State was Down-rev, you would use the Firmware Update action to update the firmware: CCSA. CCSA-2 adapters in a Nonstop S-series I/O enclosure provide SS7 connectivity to NonStop BladeSystems via IOMF2 CRU to c7000 ServerNet switch connections. Firmware is pre-installed on CCSAs in a NonStop S-series I/O enclosure. You might need to update the firmware using either OSM or SCF. The OSM Service Connection displays CCSA firmware attributes and action under the CCSA SAC object. To check or update CCSA firmware using the OSM Service Connection, locate and expand the CCSA, then select its subcomponent CCSA SAC object. Managing ServerNet Adapter Firmware 27

28 If the CCSA firmware attributes show that the current firmware Version is the same as the available Default File Version; no update is necessary. If the Compare State was Down-rev, you would use the Firmware Update action to update the firmware. For more information about the CCSA, refer to the LAN Configuration and Management Manual. See also Managing S-Series Interoperability Firmware (page 30) and the NonStop Firmware Matrices. TRSA. TRSAs in a NonStop S-series I/O enclosure provide token-ring connectivity to NonStop BladeSystems via IOMF2 CRU to c7000 ServerNet switch connections. To add or start the TRSA, use the SCF interface to the SLSA subsystem. To check and update the TRSA firmware, use the TSM Service Application as described in the Token-Ring Adapter Installation and Support Guide. For more information, refer to the LAN Configuration and Management Manual Table 7 (page 28) identifies the FCSA, G4SA, and CCSA firmware product names and their latest T-number and firmware levels. Table 7 J-Series ServerNet Adapters Firmware Information ServerNet Adapter Fibre Channel ServerNet Adapter (FCSA) Fibre Channel ServerNet Adapter (FCSA) Gigabit Ethernet 4-Port ServerNet Adapter (G4SA) 6373 Common Communication ServerNet Adapter (CCSA) Firmware FCSA flash firmware FCSA Flash Boot firmware G4SA Boot firmware SS7 firmware Latest NonStop T-Number and Firmware Level T0630G06^AAU T0612G06^AAB T0613G06^AAS T0309G08^AAF Managing SWAN and SWAN 2 Concentrator Firmware Both SWAN and SWAN2 are supported in J-series RVUs, and OSM is used to update the firmware. SCF can also be used. For procedures to update the firmware, see either the SWAN Concentrator Installation and Support Guide or the SWAN 2 Concentrator Installation and Support Guide. NOTE: Firmware levels for each component are located in the NonStop Firmware Matrices document. Managing NonStop Cluster Switch Firmware To monitor and manage a ServerNet Cluster product configured with 6780 switches, use either the OSM Service Connection or SCF commands. See the ServerNet Cluster 6780 Operations Guide for more information. For information on required software, installation, migration, and fallback procedures, see the ServerNet Cluster 6780 Planning and Installation Guide. NOTE: Check with Scout for the latest SPRs. For firmware levels, see the NonStop Firmware Matrices located in the Service Information section of the Support and Service collection of the NonStop Technical Library at 28 Managing Microcode and Firmware

29 Table 8 Updateable Firmware for the NonStop ServerNet 6770 and 6780 Cluster Switch File Names and Locations Firmware Name Component File Name Default Location Tool Router-2 ASIC* firmware 6780 Cluster Switch logic board M2789 SYSnn subvolume SCF or OSM Service Connection ServerNet Cluster 6780 Operations Guide Switch configuration firmware 6770 Cluster Switch M6770 SYSnn subvolume SCF or OSM Service Connection ServerNet Cluster 6770 Hardware Installation and Support Guide Managing CLIM Firmware and Software If your system has CLIMs attached, it is very important that your CLIM firmware is compatible with your system. Refer to the NonStop Firmware Matrices, located in the Service Information section of the Support and Service collection of the NonStop Technical Library at nonstop-docs, and ensure you have compatible firmware levels for all CLIM components. For instructions on upgrading CLIM firmware when a system is halted and when it is running, see the Cluster I/O Protocols (CIP) Configuration and Management Manual. The OSM Service Connection can be used to update firmware on individual CLIMs; the OSM Low-Level Link can be used to update software on individual CLIMs. However, the CLIM Management Tool provides a faster, more efficient method for updating CLIM software and firmware for all CLIMs on the system at the same time, while the system is down. Requirements and considerations for using the CLIM Management Tool include: You must have OSM Service Connection version T0682H02^ADP or later to update both CLIM firmware and software through the CLIM Management Tool. To do so, you must perform the Prepare for Down System CLIM Management action With OSM Service Connection version T0862H02^ADH (and subsequent pre-adp versions), you can update just the CLIM firmware while the system is down. To do so, you must perform the Prepare for Down System CLIM Firmware Update action, located under the OSM Service Connection, before shutting down the system. The CLIM Management Tool replaced the Down System CLIM Firmware Update Tool on NonStop System Console Installer DVD Update 23 and later. You can still use the Down System CLIM Firmware Tool to update CLIM firmware if you have not yet upgraded console software. It requires OSM Service Connection version T0862H02^ADH or later, and can be used to update just CLIM firmware while the system is down, regardless of the name of the Prepare... action in the OSM Service Connection. Whichever tool is available on your console can be launched from the Windows Start menu by selecting All Programs>HP OSM> followed by the name of the tool. For information on installing the CLIM Management Tool, see the NonStop System Console Installer Guide. For information on performing CLIM software/firmware updates, see the online help within the console-based tool and the OSM Service Connection you are using, plus: CLuster I/O Module (CLIM) Software Compatibility Reference Cluster I/O Protocols (CIP) Configuration and Management Manual Managing CLIM Firmware and Software 29

30 Managing S-Series Interoperability Firmware NOTE: See the NonStop Firmware Matrices for product levels. To find out if your NonStop system supports interoperability with S-series systems, see the planning guide for your system. Table 9 Updateable Firmware for S-series Interoperability. Component Firmware Name File Name Default Location Tool CCSA SS7 Controller firmware, required for connectivity with S-series systems C0309P00 SYSnn subvolume DSM/SCM and SCF PMF and PMF2; IOMF and IOMF2 Service Processor firmware, required to connect to the S-series I/O enclosure SPCODE9 SYSnn subvolume OSM Service Connection and OSM Low-Level Link 30 Managing Microcode and Firmware

31 3 Installation, Migration, and Fallback Considerations for This RVU J06.04 See the Readme file and the appropriate softdocs for the latest information on any migration or configuration steps. Considerations in this chapter are categorized according to the RVU at which they were introduced. Compiling C++ Programs to Run on RVUs Earlier Than J06.04 Objects compiled by the J06.04 and later C++ compilers might require new functions that are in the current C++ Common Runtime Library but not in RVUs earlier than J Specifically, programs that use either of the following features will fail to load because of unresolved externals (assuming that they are not linked using the rld_unresolved ignore option): A try catch block An exception specifier To 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.nn parameter on the CPPCOMP command (Guardian environment), where nn indicates the RVU on which the objects will run. NOTE: The RVU and -WRVU command line parameters do not support J-series RVUs. If J06.03 is the intended target system, specify H 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 all target 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 the T2831H01. SQL/MX Versioning Feature Removed Certain SQL/MX versioning enhancements that were introduced in an earlier H-series RVU have been 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. CLIM The CLIM is introduced in the J06.04 RVU. CLIM is a rack-mounted HP ProLiant class server that provides connectivity between the NonStop host system and either the network or the storage devices. For CLIM upgrade procedures, see the Cluster I/O Protocols (CIP) Configuration and Management Manual. For fallback procedures, see Chapter 13. CLIMs with software associated with J06.04 are not compatible with RVUs of J06.06 and later RVUs. However, if you are migrating from a J06.04 RVU to a J06.06 or later RVU, the software upgrade procedures in this manual are ordered so that the CLIM and RVU compatibility is assured because the RVU on the host is updated first, then, while the processors are halted, the CLIMs are updated to the CLIM software version associated with this RVU. When the system is loaded, the CLIM and the NonStop host are at the same level and are therefore compatible. J

32 J06.05 If the CLIM is in the STARTED state, you can determine the CLIM software version by using OSM Low-Level Link, OSM Service Connection or by entering: SCF-> VERSION CLIM $ZZCIP.clim-name If the CLIM is not in the STARTED state, you can use the CLIMCMD command with the Linux cat subcommand by entering: TACL>climcmd clim-name cat /etc/vproc Multiple versions of CLIM software are allowed on a system as long as all CLIMs have CLIM SPRs that are compatible with the host RVU. See the NonStop CLuster I/O Module (CLIM) Software Compatibility Reference for all CLIM and host RVU compatibility information. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for troubleshooting tips about identifying an incompatibility in CLIM and host CIP software. AF_UNIX Release 2 Migration and Fallback Migrating to AF_UNIX Release 2 AF_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 1 semantics remain available along with the AF_UNIX Release 2 semantics. AF_UNIX Release 1 semantics are the default semantics. You can choose which semantics to use either programmatically or 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 to start $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 the target-volume.zossins.ossinfil file by changing the line SERVER #ZPLS to * SERVER #ZPLS NOTE: NOTE: target-volume is normally $SYSTEM. #ZPLS cannot be deleted from ZOSSSERV but can be deleted from OSSINFIL. Commenting out the #ZPLS statement from the OSSINFIL prevents the STARTOSS utility from issuing an error during execution. The $ZLSnn processes are started automatically when the processors start; do not add them to any startup or shutdown scripts. 32 Installation, Migration, and Fallback Considerations for This RVU

33 Falling Back to An Earlier Version of AF_UNIX If fallback is required: If you start $ZPLS in a startup script using the SCF START SERVER command, modify startup scripts to start $ZPLS using the SCF START SERVER command. If you use the STARTOSS utility to start OSS processes, modify the target-volume.zossins.ossinfil file by changing the line * SERVER #ZPLS to SERVER #ZPLS NOTE: target-volume is normally $SYSTEM. This ensures that the OSS Socket Local Server is started correctly as system load. The OSS Monitor included in AF_UNIX Release 2 software adds database records for the local server 2 (LS2) processes. If fallback is required, HP recommends that, after the system is no longer running an RVU containing AF_UNIX Release 2, you delete these records using the SCF DELETE SERVER 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's Guide. CLuster I/O Module (CLIM) Software Compatibility CLIMs with software associated with J06.05 are not compatible with RVUs of J06.06 and later RVUs. However, if you are migrating from a J06.05 RVU to a J06.06 or later RVU, the software upgrade procedures in this manual are ordered so that the CLIM and RVU compatibility is assured because the RVU on the host is updated first, then, while the processors are halted, the CLIMs are updated to the CLIM software version associated with this RVU. When the system is loaded, the CLIM 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 OSM Low-Level Link, OSM Service Connection or by entering: SCF-> VERSION CLIM $ZZCIP.clim-name If the CLIM is not in the STARTED state, you can use the CLIMCMD command with the Linux cat subcommand by entering: TACL>climcmd clim-name cat /etc/vproc Multiple versions of CLIM software are allowed on a system as long as all CLIMs have CLIM SPRs that are compatible with the host RVU. See the NonStop CLuster I/O Module (CLIM) Compatibility Reference for all CLIM and host RVU compatibility information. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for troubleshooting tips about identifying an incompatibility in CLIM and host CIP software. J

34 J06.06 CLuster I/O Module (CLIM) Software Compatibility For J06.06 and subsequent J-series RVUs, CLIM software associated with the RVU is compatible with the current RVU and all preceding RVUs (J06.06 and above). NOTE: The NonStop host RVU is not compatible with every CLIM version. The CLIM must be at the NonStop host RVU version or above. Therefore, when you upgrade your NonStop host RVU, you must also update your CLIM to the software level associated with the RVU to which you are upgrading. If you are migrating from a J06.06 or later RVU, you can perform an online upgrade to the CLIMs before upgrading the host system. If the CLIM is in the STARTED state, you can determine the CLIM software version by using OSM Low-Level Link, OSM Service Connection or by entering: SCF-> VERSION CLIM $ZZCIP.clim-name If the CLIM is not in the STARTED state, you can use the CLIMCMD command with the Linux cat subcommand by entering: TACL>climcmd clim-name cat /etc/vproc Multiple versions of CLIM software are allowed on a system as long as all CLIMs have CLIM SPRs that are compatible with the host RVU. See the NonStop CLuster I/O Module (CLIM) Compatibility Reference for all CLIM and host RVU compatibility information. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for troubleshooting tips about identifying an incompatibility in CLIM and host CIP software. DSM/SCM Upgrade Issues/Interoperability SPR Requirements J06.07 If you are migrating from an J06.05 or earlier RVU to a J06.06 or later RVU, be aware that all the DSM/SCM target systems should be upgraded before the DSM/SCM host is upgraded. The snapshot file created by T6031H02^ACL has changed and cannot be read by earlier versions of DSM/SCM. See Support Note S09036 for more information. Falling Back to ilo Firmware T0848AAA After updating the ilo firmware to T0848AAB or later (ilo version 1.77 or later), subsequent attempts to downgrade to T0848AAA (ilo version 1.50) using OSM Service Connection will generate 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: : Process terminated with fatal errors or diagnostics Before retrying the downgrade operation, perform a CLIM Rediscovery from the OSM Service Connection to determine if the ilo firmware has actually been downgraded. The ilo firmware downgrade operation should have succeeded in most cases even though the OSM Service Connection 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 the downgrade action can be safely ignored. 34 Installation, Migration, and Fallback Considerations for This RVU

35 DSM/SCM Upgrade Issues/Interoperability SPR Requirements J06.08 If you are migrating from a J06.04 or earlier RVU to a J06.07 or later RVU, be aware that the USERID attributes of all persistent processes configured under $ZZKRN might change from SUPER.SUPER to NULL.NULL. If this occurs on a system where $SYSTEM is using FCDM disk enclosures connected by FCSAs in IOAM enclosures, the system might halt when a system load to the new RVU is attempted. To prevent this problem, you must install DSM/SCM SPR T6031H02^ACJ or later on your system. See Hotstuff HS03058 for more information. NonStop SQL/MX The J06.08 RVU introduces the large block support feature (32 KB blocks) for NonStop SQL/MX tables. 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^ACC and 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 across different RVUs are: Table 10 NonStop SQL/MX and Supported RDF Versions RVU on PRI RVU on BKUP RDF SPR on PRI RDF SPR on BKUP J06.08 J06.08 H09^ACC H09^ACC J06.03 to J06.07 J06.08 H09^ACC H09^ACC G06.03 and later J06.08 A07^ACA H09^ACC J06.09 This section describes changes to default behavior introduced by new features at J For a complete list of new features, migration issues and fallback considerations, see the J06.09 Release Version Update Compendium. SQL/MX Requires JDBC T2 Driver JDBC T2 Driver must be installed on J06.09 and later J-series RVUs to support SQL/MX BladeCluster Solution Multi-Zone Support J06.10 Multi-zone topologies, introduced at J06.09 but supported back to J06.04, require software licences and other components on all nodes within the zones. See the J06.09 Release Version Update Compendium for a high-level list of these requirements. This section provides information only for new features and changes that affect the software installation and upgrade steps for J See the J06.10 Release Version Update Compendium for a complete list of new features and associated migration and fallback alerts. NonStop SOAP 4 NonStop SOAP 4 migration issues exist for NonStop SOAP 3 to NonStop SOAP 4 upgrades. See the J06.nn Release Version Update Compendium for this RVU for a list of migration issues and workarounds. J

36 New CLuster I/O Module (CLIM) Storage Devices HP introduces (controlled availability) support for next-generation CLIMs and storage devices. The new CLIMs and storage devices require J06.06 and later J-series RVUs. All software required for these components is included with this RVU. See the planning guide for your system for information about the CLIMs and storage devices. The new devices require the J06.06 or later J-series RVU. 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.06 and J06.09 inclusive, you must add SPRs to those RVUs to support the new CLIMs and disk enclosures because falling back to a previous RVU removes the required software. For a list of required SPRs for these components, see the CLuster I/O Module (CLIM) Software Compatibility Reference. The next-generation CLIMs and storage devices only work with each other. They cannot be mixed with the previous generation CLIMs and storage devices. Other CLIM and CIP Changes The 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-pulse interfaces 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 information about these features. Hardware and Networking As of J06.03, Token-Ring and System Signaling Seven (SS7) connectivity is supported on NonStop BladeSystems through the NonStop S-series I/O enclosure. For more information, see the NonStop BladeSystem Planning Guide. New Operating System Features TMF 3.6 J06.10 adds several new operating system features, most of which have migration and fallback issues. See the J06.10 Release Version Update Compendium for more information about these features. Fallback considerations exist for TMF 3.6 enhancements. See the J06.10 Release Version Update Compendium for this RVU for more information. itp WebServer 7.2 Migration and fallback considerations exist for itp WebServer 7.2. See the J06.10 Release Version Update Compendium for this RVU for more information. Expand Enhancements. J06.11 Fallback considerations exist for the Expand enhancements. See the J06.10 Release Version Update Compendium for more information. This section provides information only for new features and changes that affect the he software installation and upgrade steps for J See the J06.11 Release Version Update Compendium for a complete list of new features and associated migration and fallback alerts. 36 Installation, Migration, and Fallback Considerations for This RVU

37 Changes to SSOCLIM Privilege Requirement J06.12 HP SUM The privilege for running SSOCLIM, which was SUPER.SUPER for J06.09 and J06.10, has been changed to any SUPER group user. SSOCLIM is run after a fallback. For details, see Complete CLIM Set Up in Chapter 13: Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations (page 119). This section provides information only for new features and changes that affect the software installation and upgrade steps for J See the J06.12 Release Version Update Compendium for a list of new features and associated migration and fallback alerts. The introduction of HP SUM affects upgrade steps for NonStop NS2200 series, NS2100, and NonStop BladeSystem NB54000c and NB54000c-cg servers. See Chapter 4: Upgrade Checklist (page 41) and Perform Updates (page 93). Considerations for Fallback to J06.11 J06.13 Safeguard Fallback considerations exist for NonStop BladeSystem NB54000c and NB54000c-cg systems falling back to J See support note S This section provides information only for new features and changes that affect the software installation and upgrade steps for J See the J06.13 Release Version Update Compendium for a list of new features and associated migration and fallback alerts. Fallback and migration considerations exist for the new Safeguard features. See the J06.13 Release Version Update Compendium for more information. Considerations for Fallback to J06.11 Fallback considerations exist for NonStop BladeSystem NB54000c and NB54000c-cg systems falling back to J See support note S Performance Tuning Requirements Steps to tune performance exist on certain combinations of NonStop servers and J-series RVUs. See Support Note S11044 for more information. Core License File The core licensing option on BladeSystems NB54000c and NB54000c-cg, first introduced and required with J06.13, affects installation steps. For more information about the core license file, refer to the NonStop BladeSystem Planning Guide. Migrating a NonStop BladeSystem NB50000c to an NB54000c or NB50000c-cg to an NB54000c-cg The core license file requires the CLICVAL tool, which affects preparation steps. For more information, see Upgrade Checklist (page 41), Preparing to Upgrade the Server Software (Preinstallation Tasks) (page 46), and the NonStop BladeSystem Planning Guide. J

38 Upgrading a NonStop BladeSystem NB54000c or NB54000c-cg to J06.13 or Later RVUs Before upgrading to the J06.13 RVU or a later RVU, you must obtain the Core License Validation tool (CLICVAL). For more information, refer to the NonStop BladeSystem Planning Guide. Before upgrading to J06.13 or a later J-series RVU, use the CLICVAL tool to verify that the core license file is valid. After upgrading to J06.13 or later J-series RVU, HP recommends that you use the OSM action, Read Core License to verify that the core license is valid. See the upgrade checklist in Upgrade Checklist (page 41). HP NonStop Software Essentials HP NonStop Software Essentials is a software installation and management tool for NonStop servers. Installed as a plug-in to HP SIM, NonStop Software Essentials uses DSM/SCM server software and provides a replacement for certain DSM/SCM Planner Interface functions that is more secure, easier to use, and overcomes other shortcomings of DSM/SCM. It coexists with DSM/SCM; you can use either NonStop Software Essentials or the DSM/SCM Planner Interface for tasks in which there is overlapping functionality. For more information, see the NonStop Software Essentials Installation and Quick Start Guide. IB CLIM Fallback Considerations EXTDECSL The IB CLIM is supported as of J If you fall back to J06.12 and have IB CLIMs, after you reimage the CLIMs, you must select Open for mode and the CLIM model should show 3 copper 2 IB. See Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations (page 119). An SPR for T9003H01, ACC, exists in J If the application is using any of the new features introduced by this SPR, the application requires recompilation. If the application is not using any of the new features introduced by this SPR, recompilation using the SPR preceding the current SPR is enough. If the application is using any of the new features, remove the new features before recompiling the application with a prior SPR of EXTDECS. TNS/E ECOBOL J06.14 An SPR for T0356H01, ABI, exists in J To fall back to a prior RVU, after fallback, recompile the application with the ECOBOL SPR that precedes this SPR. This section provides information only for new features and changes that affect the software installation and upgrade steps for J See the J06.14 Release Version Update Compendium for a list of new features and associated migration and fallback alerts. Halt and Hard Reset Processors When Upgrading to J06.14 When upgrading to J06.14 or a later J-series RVU from J06.13 or an earlier RVU, the processors must be hard reset after they are halted and before loading the system as described in 5. (Required Only for Upgrade from J06.13 or Earlier to J06.14 or Later) Perform a Hard Reset (page 97). HP Power Regulator J06.14 is the first RVU to support Power Regulator. For more information, see Fallback Considerations for the Power Regulator (page 119). 38 Installation, Migration, and Fallback Considerations for This RVU

39 Safeguard Fallback and migration considerations exist for the new Safeguard features. See the J06.14 Release Version Update Compendium for more information. SQL/MX Release 3.2 J06.15 SQL/MX Release 3.2 replaces SQL/MX Release as the default SQL/MX version on the SUT starting with J Users have a choice of staying with the latest SQL/MX Release SPRs released as Time Critical Fixes (TCFs) or to migrate to SQL/MX Release 3.2. Please refer to the instructions in hotstuff HS03173 for more details before installing J NOTE: Starting with SQL/MX Release 3.2, mxtool includes the fixmxcsmd option, which supports the conversion of the SQL/MX Release 2.3.x CPU list format to the SQL/MX Release 3.2.x CPU list format in the ENVIRONMENTVALUES MXCS metadata table. To perform the CPU list format conversion, you must run the mxtool command with the fixmxcsmd option as described in the SQL/MX Connectivity Service Manual for SQL/MX Release 3.2. This section provides information only for new features and changes that affect the software installation and upgrade steps for J See the J06.15 Release Version Update Compendium for more information about these and other J06.15 products and their associated migration and fallback alerts. CLIM Fallback Considerations for Multiple Providers per CLIM Gen8 CLIMs Multiple Providers per CLIM functionality and the requirements for CLIM fallback from J06.15 to an earlier RVU are described in If Falling Back to J06.14 or an Earlier RVU (page 120). The Gen8 CLIMs are first supported with the J06.15 RVU and are available in IP, Storage, and Telco versions. They are not supported on H-series RVUs. For more information about Gen8 CLIMs, see the CLuster I/O Module (CLIM) Installation and Configuration Guide. NOTE: If you have the J06.08 through J06.14 RVU installed and are not planning to migrate to J06.15 or a later J-series RVU, you can implement Gen8 functionality and support by installing the SPR required for your current RVU as identified in the CLuster I/O Module (CLIM) Installation and Configuration Guide. Halt and Hard Reset Processors When Upgrading to J06.15 When upgrading to J06.15 from J06.13 or an earlier RVU, the processors must be hard reset after they are halted and before loading the system as described in 5. (Required Only for Upgrade from J06.13 or Earlier to J06.14 or Later) Perform a Hard Reset (page 97). NonStop Server for Java 7.0 NonStop Server for Java 7.0 (NSJ7) is the first release of NonStop Server for Java to be delivered via RVU instead of as an independent product and supports the latest Java SE 7 standard. For information about NSJ7 features, see the NonStop Server for Java 7.0 Programmer Reference and the NonStop Server for Java 7.0 Tools Reference. NonStop SOAP 4.1 See the J06.15 Release Version Update Compendium for information about NonStop SOAP 4.1. J

40 NonStop Software Essentials Safeguard NonStop Software Essentials is provided on the J06.15 SUT and includes these and other new features: Viewing Upgrouped Packages has been added to the Host Navigation Pane under the Software in Archive Node. This application-defined group contains a list of all software packages in the archive that do not currently belong to any user-defined package group. $ZTC0 has been removed as a default stack. NonStop Software Essentials runs on $ZTCP0 and $ZTCP1 by default. You can add other stacks for use by NonStop Software Essentials For more information about NonStop Software Essentials 2.1.0, see the NonStop Software Essentials Installation and Quick Start Guide. Safeguard provides several enhancements for J For details, see the Safeguard Administrator s Manual, the Safeguard Audit Service Manual, the Safeguard Reference Manual, and the Safeguard Management Programming Manual. Fallback and migration considerations for new Safeguard features are described in the J06.15 Release Version Update Compendium. SQL/MX Release SQL/MX Release replaces SQL/MX Release 3.2 as the default SQL/MX version on the SUT starting with J See the SQL/MX Release manuals for product details. NOTE: Starting with SQL/MX Release 3.2, mxtool includes the fixmxcsmd option, which supports the conversion of the SQL/MX Release 2.3.x CPU list format to the SQL/MX Release 3.2.x CPU list format in the ENVIRONMENTVALUES MXCS metadata table. If you are migrating directly from SQL/MX Release to SQL/MX Release 3.2.1, you need to perform the CPU list format conversion by running the mxtool command with the fixmxcsmd option as described in the SQL/MX Connectivity Service Manual for SQL/MX Release Installation, Migration, and Fallback Considerations for This RVU

41 4 Upgrade Checklist Use the upgrade checklist in Upgrade Checklist (page 42) to track your progress as you perform the tasks required to upgrade to this RVU and the checklists in Table 11 and Table 12 (page 42) to record the information needed when performing these tasks. CAUTION: The upgrade steps must be performed in the order specified in this chapter. NOTE: To perform these upgrade tasks, you need the NonStop System Console (NSC) Installer Guide. If your system has CLIMs, you also need the Cluster I/O Protocols (CIP) Configuration and Management Manual the CLuster I/O Module (CLIM) Software Compatibility Reference, and the NonStop Firmware Matrices. NOTE: If you are migrating from a J06.06 or later RVU, you can perform an online upgrade of the CLIMs before upgrading the host system. (See the Cluster I/O Protocols (CIP) Configuration and Management Manual for online CLIM software upgrade procedures.) If you have not already upgraded 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 for IOMF2 PMF CRUs. Required Information Checklists Gather the information in Table 11 before you start. Obtain firmware levels from the CLuster I/O Module (CLIM) Software Compatibility Reference. Table 11 Required Information Checklist, Before You Start Type of Information Value 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, VIO, org16sefirmware ME firmware ME FPGA firmware SWAN firmware Required Information Checklists 41

42 Table 11 Required Information Checklist, Before You Start (continued) Type of Information Value SWAN2 firmware ServerNet Cluster firmware Cluster Switch Cluster Switch (logic board; router-2) SS7 Controller firmware DSM/SCM product version (server and client) Processor type Record the information in Table 12 while you perform the upgrade. Table 12 Information to Gather During the Upgrade (Checklist) Type of Information Value 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 Checklist Go through this list in order and check off each task in the Done column after it is complete. Table 13 Upgrade Checklist Task Description Reference Done? 1. Perform all the necessary pre-installation tasks before updating the system console and receiving the SUT. Preparing to Upgrade the Server Software (Preinstallation Tasks) (page 46) 2. Before you receive and install the SUT, first copy the DSM/SCM server and client product SPR and SWID SPR from the SUT to your host system. 3. Back up important files. 4. Record the current SYSnn. 5. Save current system configuration file. 6. Install required or recommended fallback SPRs and node interoperability SPRs, if necessary. 7. Upgrade system console software. Appendix C: Copying the DSM/SCM, NonStop Software Essentials, and SWID SPRs from the SUT Using NonStop Software Essentials Copying the DSM/SCM and SWID SPRs from the SUT Using the Planner Interface (page 156) Back Up Important Files (page 46) Record the Current SYSnn (page 47) and Table 11 (page 41) Save the Current Configuration File (CONFxxyy) (page 47) Using DSM/SCM With NonStop Software Essentials to Install SPRs (page 133) or Using DSM/SCM With the Planner Interface to Install SPRs (page 140) (procedures) Install Node Interoperability SPRs (page 54) (list of required SPRs) Updating System Consoles (Optional) (page 15) 42 Upgrade Checklist

43 Table 13 Upgrade Checklist (continued) Task Description 8. If you are migrating from a pre-j06.13 RVU to NB54000c or NB54000c-cg, use the CLICVAL tool to verify your license file. Reference 1. Prior to upgrading to J06.13, use the CLICVAL tool to verify the core license file is valid. For more information on using CLICVAL, refer to the TACL Reference Manual and NonStop BladeSystem Planning Guide. Note: If CLICVAL cannot verify your core license file, you must order a new one as described in the NonStop BladeSystem Planning Guide. 2. After upgrading to J06.13 or a later RVU for NB54000c or NB54000c-cg, HP recommends that you use the OSM Read Core License action to verify that the core license is valid. Later in this checklist, you will be reminded to perform this action. IMPORTANT: If your license file is invalid or missing, you must correct this problem. For more information, refer to the NonStop BladeSystem Planning Guide. Done? 9. Install and configure the latest NonStop System Console (NSC) Installer Guide Halted State Services firmware, if (procedures) necessary (includes DISKBOOT and ISP1040 firmware). Note: This step NonStop Firmware Matrices (firmware levels reference) is not applicable to NonStop NS2000 series systems. 10. Verify system operations. 11. Install CLIM software on NonStop System Console. 12. For those with NonStop Software Essentials, receive this RVU SUT into the DSM/SCM software archive. 13 For those with the DSM/SCM Planner Interface, receive this RVU SUT into the DSM/SCM archive. 14. For those with NonStop Software Essentials, create this RVU software configuration revision. 15. For those with the DSM/SCM Planner Interface, create this RVU software configuration revision. 16. For those with NonStop Software Essentials, build and apply this RVU software revision. 17. For those with the DSM/SCM Planner Interface, build and apply this RVU software revision. 18. Print DSM/SCM Operator Instructions Prepare for down system CLIM firmware and/or software update by performing the appropriate action in the OSM Service Connection. 20. Run ZPHIRNM. Verify System Processes (page 48) Cluster I/O Protocols (CIP) Configuration and Management Manual (installation procedures), CLuster I/O Module (CLIM) Software Compatibility Reference (CLIM software and firmware compatibility information) Receive New Software Into the Archive (page 58) Receive New Software Into the Archive (page 70) Create a New Software Revision (page 61) Create a New Software Revision (page 74) Build and Apply the New Software Revision (page 64) Build and Apply the New Software Revision (page 77) Print Operator Instructions From the Target Interface (ZPHITI) (page 66) Managing CLIM Firmware and Software (page 29) OSM Service Connection online help Chapter 8: Running ZPHIRNM Upgrade Checklist 43

44 Table 13 Upgrade Checklist (continued) Task Description 21. Halt the processors. 22. (Optional) Update system firmware using HP SUM (this applies to all NonStop systems running J-series software except the NS2000 series, but is not always required). Reference 2. Halt the Processors (page 96) 3. (Conditional): Update the System Firmware (page 96) NonStop Firmware Matrices Done? 23. (Optional) Update the system firmware manually (applicable to NonStop NB50000c servers only but not always required). See the sections Valid System Firmware and HSS Combinations and Updating BL860c Blade Firmware in the NonStop Firmware Matrices. 24. If Halted State Services firmware is being upgraded, hard reset the processors. Note: This step is not normally applicable to NonStop NS2000 series systems except that a reset is required if upgrading to J06.14 or a later RVU. If you have already performed Step 22 (updating system firmware using HP SUM) as part of upgrading any other NonStop system running J-series software, a power cycle has already occurred and no hard reset of processors is required. 25. Update c7000 Enclosure firmware, if necessary. 4. (Conditional): Update the HSS Firmware (page 96) This update is done through a Field Change Order (FCO). 26. If a hard reset of the processors was successful step 24, a reset is not required again, including for systems running J06.14 or a later RVU. If it was not successful, perform this procedure. 27. Update CLIM software on all CLIMs by performing a CLIM software upgrade using the OSM Low-Level Link. (If you are migrating from J06.06 or later and performed an online upgrade of the CLIM to the CLIM software released with this RVU before starting the host system upgrade, you can skip this step.) 5. (Required Only for Upgrade from J06.13 or Earlier to J06.14 or Later) Perform a Hard Reset (page 97) 6. Upgrade the CLIM Software (page 98) Cluster I/O Protocols (CIP) Configuration and Management Manual 28. Update firmware for CLIM components, if necessary. 29. Load the system with this new RVU. 30. For NonStop BladeSystem NB54000c and NB54000c-cg, verify the system's core license file. 31. Update S-series interoperability firmware, if necessary. 7. (Optional) Update the CLIM Firmware (page 98) Cluster I/O Protocols (CIP) Configuration and Management Manual 8. Loading the System (page 98) Use the OSM Read Core License action to verify that the core license is valid. IMPORTANT: If your license file is invalid or missing, you must correct this problem. For more information, refer to the NonStop BladeSystem Planning Guide. Managing S-Series Interoperability Firmware (page 30) 44 Upgrade Checklist

45 Table 13 Upgrade Checklist (continued) Task Description 32. Update ME and ME FPGA firmware, if necessary. 33. For systems with IOAMs, update IOAM firmware, if necessary. 34. Update FCSA firmware, if necessary. 35. Update G4SA Boot firmware, if necessary. 36. Update remaining server blade firmware, if necessary. 37. Update G4SA Download Code firmware, if necessary. 38. Recover TCP/IP files, if necessary. 39. Check processor status. 40. Configure WANMGR, if necessary. 41. Update SWAN concentrator CLIP firmware, if necessary. 42. Start system software. 43. Configure OSS, if necessary. 44. Configure SMF, if necessary. 45. Configure RDF, if necessary. Set Up itp WebServer (page 109) 47. Re-deploy NonStop SOAP 4, if installed on the previous RVU. 48. Start applications. Reference Updating ME Firmware (page 22) Managing ME Firmware and ME FPGA Firmware (page 22) and the CSSI web page Managing ServerNet Adapter Firmware (page 25) Managing ServerNet Adapter Firmware (page 25) This update is done through a Field Change Order (FCO). Managing ServerNet Adapter Firmware (page 25) Update NonStop TCP/IP Configuration Files (page 105) Check Processor Status (page 48) Configure the WAN Manager (page 108) SWAN Concentrator Installation and Support Guide or SWAN 2 Concentrator Installation and Support Guide Start System Applications (page 103) Configure OSS (page 107) Configure SMF (Optional) (page 108) Configure the Remote Database Facility (page 108) Re-deploy NonStop SOAP 4 (page 109) Done? Upgrade Checklist 45

46 5 Preparing to Upgrade the Server Software (Preinstallation Tasks) Before updating the system console and receiving the SUT, perform these tasks: Back Up Important Files Before you upgrade, create tape backups of critical host applications and files. Back Up NonStop SQL/MP HP recommends that you always have a current backup copy of the $SYSTEM.SYSTEM.ZZSQLCI2 file in case you need to initialize SQL later if you have problems with your new RVU during or after installation. 1. 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 files See the NonStop SQL/MX Release 3.2 Installation and Upgrade Guide. Back Up Spooler Control files Before executing the SPOOLCOM;SPOOLER,DRAIN command: Use the SPOOLCOM;COLLECT $collector-process, LISTOPENS command to identify processes that currently have jobs open. Use the SPOOLCOM;JOB (STATE PRINT) command to determine which jobs are currently printing. Take the appropriate action to ensure that these jobs either terminate when finished or are stopped. CAUTION: To maintain the integrity of the spooler environment, wait until the Spooler has finished draining rather than stop any spooler processes by using the TACL STOP command. The control file 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 Files Use the OBEYFORM option available in TMFCOM INFO commands to save current configuration information in command files. Back Up CLIM Configuration Files Back up CLIM configuration files for each CLIM using the TACL command CLIMBKUP. 46 Preparing to Upgrade the Server Software (Preinstallation Tasks)

47 NOTE: If you must fall back to this RVU, you need to restore these saved configuration files because the configuration file version must match the NonStop system RVU. If you are upgrading from J06.04 or J06.05, create a subvolume to store the backups, then rename each backup file after you create it. The default file name for the backup is backupgz. Rename these as you create them. For example: 1. CLIMBKUP N $DATA1.BCKJ FUP RENAME $DATA1.BCKJ0605.BACKUPGZ, $DATA1.BCKJ0605.N CLIMBKUP N $DATA1.BCKJ FUP RENAME $DATA1.BCKJ0605.BACKUPGZ, $DATA1.BCKJ0605.N For upgrades from J06.06, you can specify a unique filename in the same command. For example, >CLIMBKUP N $system.n bckj0606 Record the Current SYSnn Identify and record the current SYSnn subvolume on your system. You will have to specify this SYSnn subvolume if you need to fall back from this RVU. At a TACL prompt, issue the status command to determine the current SYSnn subvolume. For example: 3> status 0,0 System \ELI Process Pri PFR %WT Userid Program file Hometerm 0,0 201 P R ,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 CONFIG file, saved for future use. For fallback purposes, save a copy of the current CONFIG file by using a unique file name. Do not omit this step. You can use the saved configuration file to return to an earlier, stable configuration. If you need to fall back to the previous RVU, you must load the system by using a saved configuration file and the 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 This example saves the current system configuration to the file $SYSTEM.ZSYSCONF.CONF1101: -> SAVE CONFIGURATION 11.1 The configuration file $SYSTEM.ZSYSCONF.CONF1101 has been created. Record the Current SYSnn 47

48 Verify System Processes Check Processor Status 1. Log on to the OSM Low-Level Link. The OSM Low-Level Link appears. 2. Select Processor Status. The Processor Status dialog box appears. The Processor Status for all processors should be Executing NonStop OS. Check System Components 1. Log on to the OSM Service Connection. See the OSM Configuration Guide if you have any problems accessing OSM. After the browser session begins, you can close the original IE window. 48 Preparing to Upgrade the Server Software (Preinstallation Tasks)

49 The system name box in the Physical view indicates the overall health of a system by the color of the system icon. Green indicates no problems reported by OSM. Yellow indicates a possible system problem. 2. Double-click to expand the object further to identify components that require attention (yellow or a yellow arrow) or immediate service (red). CAUTION: If a red triangle appears over an object, or if any component is highlighted in red, contact your HP authorized service provider. 3. 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 the Processor Halt Codes Manual. Verify System Processes 49

50 Verify the State of the Internal ServerNet Fabric To verify that the paths and connections within the ServerNet system area network (ServerNet SAN) are properly functional: 1. Log on to the OSM Service Connection. 2. In the tree pane, expand the System object to check for alarms on both Internal ServerNet Fabric objects. 3. Diagnose and resolve any problems that are causing the alarm. If necessary, contact your HP authorized service provider before continuing with the migration. Verify Firmware Use the OSM Service Connection to verify that all updateable firmware is at the proper revision level for your current RVU. For more information on updating firmware, see Managing Server Blade Firmware and Blade Element Firmware (page 24) and the OSM Service Connection User s Guide. Verify Critical System Processes From a TACL prompt, log on to the system using the super ID (255,255). Enter the LISTDEV command: QA2100.$SYSTEM.STARTUP 1> scf SCF - T9082H01 - (23JUN11) (02MAY11) - 01/17/ :44:02 System \QA2100 (C) 1986 Tandem (C) 2006 Hewlett Packard Development Company, L.P. (Invoking \QA2100.$MAINT.ZQATOOLS.TIPCFSCF) 1-> listdev LDev Name PPID BPID Type RSize Pri Program 0 $0 0,3 1,3 ( 1,0 ) \QA2100.$SYSTEM.SYS00.OPCOLL 1 $NCP 0,14 1,13 (62,6 ) \QA2100.$SYSTEM.SYS00.NCPOBJ 3 $YMIOP 0,5 1,5 ( 6,4 ) \QA2100.$SYSTEM.SYS00.TMIOP 5 $Z0 0,7 1,7 ( 1,2 ) \QA2100.$SYSTEM.SYS00.OCDIST 6 $SYSTEM 0,257 1,257 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 7 $ZOPR 0,8 1,8 ( 1,0 ) \QA2100.$SYSTEM.SYS00.OAUX 79 $ZZKRN 0,302 1,417 (66,0 ) \QA2100.$SYSTEM.SYS00.OZKRN 81 $ZZWAN 0,299 1,373 (50,3 ) \QA2100.$SYSTEM.SYS00.WANMGR 82 $ZZSTO 0,300 1,418 (65,0 ) \QA2100.$SYSTEM.SYS00.TZSTO 83 $ZZLAN 0,301 1,374 (43,0 ) \QA2100.$SYSTEM.SYS00.LANMAN 84 $ZZCIP 0,362 1,356 (74,0 ) \QA2100.$SYSTEM.SYS00.CIPMAN 106 $ZSNET 0,302 1,417 (66,0 ) \QA2100.$SYSTEM.SYS00.OZKRN 107 $ZSLM2 0,297 1,339 (67,0 ) \QA2100.$SYSTEM.SYS00.TZSLM2 108 $ZPTY 2,417 3,395 (46,0 ) \QA2100.$SYSTEM.ZSSH.STN 109 $ZPMON 0,365 (24,0 ) \QA2100.$SYSTEM.SYS00.OSSMON 113 $ZNET 0,18 1,17 (50,63) \QA2100.$SYSTEM.SYS00.SCP 126 $ZM03 3,289 (45,0 ) \QA2100.$SYSTEM.SYS00.QIOMON 50 Preparing to Upgrade the Server Software (Preinstallation Tasks)

51 127 $ZM02 2,289 (45,0 ) \QA2100.$SYSTEM.SYS00.QIOMON 128 $ZM01 1,290 (45,0 ) \QA2100.$SYSTEM.SYS00.QIOMON 129 $ZM00 0,304 (45,0 ) \QA2100.$SYSTEM.SYS00.QIOMON 130 $ZLOG 0,361 1,427 ( 1,0 ) \QA2100.$SYSTEM.SYS00.EMSACOLL 179 $ZCM03 3,365 (74,1 ) \QA2100.$SYSTEM.SYS00.CIPMON 180 $ZCM02 2,333 (74,1 ) \QA2100.$SYSTEM.SYS00.CIPMON 181 $ZCM01 1,386 (74,1 ) \QA2100.$SYSTEM.SYS00.CIPMON 182 $ZCM00 0,369 (74,1 ) \QA2100.$SYSTEM.SYS00.CIPMON 183 $YOSQA37 0,321 1,357 (63,0 ) \QA2100.$SYSTEM.SYS00.LHOBJ 184 $YOSQA3 0,314 1,363 (63,0 ) \QA2100.$SYSTEM.SYS00.LHOBJ 186 $SUITES 1,334 0,344 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 187 $SUITE2 2,311 3,337 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 188 $SQL11 3,334 2,301 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 189 $SQL10 2,302 3,332 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 190 $SQL09 1,331 0,345 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 191 $SQL08 0,346 1,329 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 192 $SQL07 3,330 2,303 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 193 $SQL06 2,304 3,326 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 194 $SQL05 1,326 0,347 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 195 $SQL04 0,348 1,324 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 196 $SQL03 3,324 2,305 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 197 $SQL02 2,306 3,322 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 198 $SQL01 1,322 0,349 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 199 $SQL00 0,350 1,319 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 200 $SCALE1 0,313 1,364 (63,0 ) \QA2100.$SYSTEM.SYS00.LHOBJ 201 $SAS313 3,320 2,307 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 202 $SAS301 2,308 3,317 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 203 $SAS125 2,309 3,315 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 205 $QA2200 0,319 1,359 (63,0 ) \QA2100.$SYSTEM.SYS00.LHOBJ 206 $POSQA1 0,320 1,358 (63,0 ) \QA2100.$SYSTEM.SYS00.LHOBJ 207 $PITSMP1 0,312 1,365 (63,0 ) \QA2100.$SYSTEM.SYS00.LHOBJ 208 $OSS3 3,313 2,310 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 209 $OSS2 2,291 3,311 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 210 $OSS1 1,317 0,351 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 211 $OSS 0,322 1,315 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 231 $MAINT 0,323 1,312 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 232 $LRGQA 0,317 1,361 (63,0 ) \QA2100.$SYSTEM.SYS00.LHOBJ 233 $KMSF1 0,324 1,307 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 234 $J06ALT 2,292 3,309 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 235 $J0617 2,293 3,307 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 236 $J0616 2,294 3,304 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 237 $J0614 0,325 1,304 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 238 $GUEST 3,301 2,295 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 239 $FULL 3,299 2,296 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 240 $EMPTY2 3,297 2,297 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 241 $EMPTY1 2,298 3,295 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 242 $DUMP3 1,302 0,326 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 243 $DUMP2 1,300 0,327 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 244 $DUMP1 1,298 0,328 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 246 $BLSYSQA 0,318 1,360 (63,0 ) \QA2100.$SYSTEM.SYS00.LHOBJ 247 $BLSCALE 0,310 1,367 (63,0 ) \QA2100.$SYSTEM.SYS00.LHOBJ 248 $BLISTER 0,315 1,362 (63,0 ) \QA2100.$SYSTEM.SYS00.LHOBJ 249 $BLESSIT 0,311 1,366 (63,0 ) \QA2100.$SYSTEM.SYS00.LHOBJ 250 $AUDTR4 3,293 2,299 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 251 $AUDTR3 2,300 3,291 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 252 $AUDTR2 1,296 0,329 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 253 $AUDTR1 0,330 1,294 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 254 $AUDIT 0,331 1,292 ( 3,51) \QA2100.$SYSTEM.SYS00.TSYSDP2 268 $ZTCP0 0,424 1,419 (48,0 ) \QA2100.$SYSTEM.SYS00.CIPSAM 293 $ZTC0 0,450 1,391 (48,0 ) \QA2100.$SYSTEM.SYS00.CIPSAM 295 $ZTN0 0,451 1,413 (46,0 ) \QA2100.$SYSTEM.SYS00.TELSERV 296 $ZOLHD 0,531 1,448 ( 1,30) \QA2100.$SYSTEM.SYS00.EMSDIST 299 $ZTNP0 0,455 1,421 (46,0 ) \QA2100.$SYSTEM.SYS00.TELSERV 300 $ZTCP1 1,422 0,456 (48,0 ) \QA2100.$SYSTEM.SYS00.CIPSAM 302 $ZTNP1 1,426 0,458 (46,0 ) \QA2100.$SYSTEM.SYS00.TELSERV 331 $ZEXP 0,61 1,38 (63,30) \QA2100.$SYSTEM.SYS00.OZEXP 350 $ZRD9 1,447 2,427 ( 1,30) \QA2100.$SYSTEM.SYS00.EMSDIST 918 $ZHOMR 0,89 ( 6,30) \QA2100.$SYSTEM.ZSYSEX.HOMER 2-> Verify System Processes 51

52 Verify Disk Drives 1. Enter the SCF STATUS DISK command: > SCF STATUS DISK $* 2. Verify that the STATUS DISK display includes all the disk drives and that the primary, backup, mirror, and mirror-backup paths are all described as STARTED: $SYSTEM TOOLS 48> SCF STATUS DISK $* SCF - T9082H01 - (01MAY08) (15MAR08) - 07/06/ :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 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 that the tape drive is online before continuing with installing SPRs, RVUs, or RVURs. OSM does not test tape 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 52 Preparing to Upgrade the Server Software (Preinstallation Tasks)

53 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 State 1. Enter the SCF STATUS CLIM command: -> STATUS CLIM $ZZCIP.* 2. Verify that the state of all configured CLIMs is STARTED: CIP Status CLIM \MYSYS.$ZZCIP.* Name Present State Trace N Yes STARTED OFF N Yes STARTED 1, 2 N Yes STARTED 2 Verify That the CIP Providers Are in the Started State 1. 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 ZCSAM STARTED Started OFF PROV1 STARTED Invalid (0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15) Check the Status of the Spooler Collector Check that the spooler collector is active and not 100 percent full. At a TACL prompt, start SPOOLCOM and issue a COLLECT, STATUS command. For example: 1> spoolcom $spls; collect, status COLLECT STATE FLAGS CPU PRI UNIT DATA FILE %FULL $S ACTIVE 3, $OPS0.SPL.DATA 44 Check for Sufficient Swap File Space You must ensure that you have configured kernel-managed swap files of sufficient size for all your system and application software processes. The optimal amount of swap space varies, depending on the configuration of your system. You must be a super-group user (255, n) in order to change the KMSF configuration by adding, altering, stopping, or deleting swap space. Only one super-group user 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 file usage. See the Kernel-Managed Swap Facility (KMSF) Manual for information on configuring swap file space. To check the size of the configured swap files for each processor: 1. At a TACL prompt, start NSKCOM: $SYSTEM STARTUP 5> nskcom NSKCOM - T5838H01 BASE (01OCT07) - Apr Copyright 1995 Compaq Computer Corporation $SYSTEM.SYSTEM.ZSYSCFG KMS.SWAPFILE = 0 $SYSTEM.ZSYSSWAP.SWAP00 Verify System Processes 53

54 KMS.SWAPFILE = 1 $SYSTEM.ZSYSSWAP.SWAP01 KMS.SWAPFILE = 2 $SYSTEM.ZSYSSWAP.SWAP02 KMS.SWAPFILE = 3 $SYSTEM.ZSYSSWAP.SWAP03 2. Issue the STATUS SWAPFILE * command to display the peak pages reserved so that you can compare that information to the total amount of swap space available. $SYSTEM TOOLS 50> nskcom STATUS SWAPFILE * NSKCOM - T5838H01 BASE (01OCT07) - Jun Copyright 1995 Compaq Computer Corporation $SYSTEM.SYSTEM.ZSYSCFG KMS.SWAPFILE = 0 $SYSTEM.ZSYSSWAP.SWAP00 KMS.SWAPFILE = 1 $SYSTEM.ZSYSSWAP.SWAP01 KMS.SWAPFILE = 2 $SYSTEM.ZSYSSWAP.SWAP02 KMS.SWAPFILE = 3 $SYSTEM.ZSYSSWAP.SWAP03 Status of $SYSTEM.ZSYSSWAP.SWAP00 CPU 0 CPU Pages: Total * Reserved Available Peak CPU Pages ever reserved Threshold CPU pages * Default swapfile extents may not be fully allocated. Status of $SYSTEM.ZSYSSWAP.SWAP01 CPU 1 CPU Pages: Total * Reserved Available Peak CPU Pages ever reserved Threshold CPU pages * Default swapfile extents may not be fully allocated. Status of $SYSTEM.ZSYSSWAP.SWAP02 CPU 2 CPU Pages: Total * Reserved 6361 Available Peak CPU Pages ever reserved 7280 Threshold CPU pages * Default swapfile extents may not be fully allocated. Status of $SYSTEM.ZSYSSWAP.SWAP03 CPU 3 CPU Pages: Total * Reserved 5242 Available Peak CPU Pages ever reserved 6863 Threshold CPU pages * Default swapfile extents may not be fully allocated.. Install Node Interoperability SPRs Node interoperability is the ability of the nodes (systems) in an Expand network to communicate and interact with each other. An Expand network can be interconnected using various technologies such as Expand over IP and ServerNet Cluster. See the NonStop Networking Overview for more information about and diagrams of NonStop platform interoperability. In addition to interoperability issues for nodes connected through Expand, there are software migration and software management issues to consider, such as accelerating TNS object files on a system running an RVU series for posterior use in a system running another RVU series, DSM/SCM software management in an environment composed of systems running different RVU series, and moving objects built on a system running an RVU series to a system running another RVU series by means of Expand, FTP, or media such as magnetic tapes. NOTE: This manual does not list the SPRs needed for BladeCluster Solution interoperability. For specific SPRs required for the BladeCluster Solution, see the BladeCluster Solution Manual. 54 Preparing to Upgrade the Server Software (Preinstallation Tasks)

55 These SPRs must be installed on systems running G-series RVUs if you want the functionality it makes available through Expand-connected H-series or J-series RVU systems. Table 14 Interoperability SPRs for G-Series RVU Systems Connected Through Expand to H-Series or J-Series RVU Systems Minimum SPR Product Name Description Introduced in this RVU T9205D46^ACF TACL Required for remote NEWPROCESS of OCA objects* G06.26 *T9205D46^ACF is required only if you want the functionality it provides. These SPRs must be installed on systems running H-series RVUs for compatibility and interoperability through a ServerNet Cluster with systems running J-Series RVUs. Table 15 Interoperability SPRs for H-Series RVU Systems Connected through ServerNet to J-Series RVU Systems Minimum SPR Product Name Description Introduced in this RVU T0294H01^AAW SNETMON Required for ServerNet clustering* H06.14 T0502H01^AAW SANMAN Required for ServerNet clustering* H06.14 *For more details, see the ServerNet Cluster Supplement for HP Integrity NonStop BladeSystems. To find out if your NonStop server supports ServerNet clustering, see the planning guide for your NonStop server. These specific SPRs must be installed on systems running G-series RVUs for compatibility and interoperability through a ServerNet Cluster with systems running J-Series RVUs. Table 16 Interoperability SPRs for G-Series RVU Systems Connected through ServerNet to J-Series RVU Systems Minimum SPR Product Name Description Introduced in this RVU T0294G08^AAX SNETMON Required for ServerNet clustering* G06.31 T0502G08^AAX SANMAN Required for ServerNet clustering* G06.31 T0682G06^AAA OSM Service Connection Suite Required for ServerNet clustering* G06.25 *For more details, see the ServerNet Cluster Supplement for HP Integrity NonStop BladeSystems. To find out if your NonStop 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 interoperability through a ServerNet Cluster with systems running H-Series RVUs. Table 17 Interoperability SPRs for G-Series RVU Systems Connected through ServerNet to H-Series RVU Systems Minimum SPR Product Name Description Introduced in this RVU T0294G08^AAP SNETMON Required for ServerNet clustering* G06.26 T0502G08^AAN SANMAN Required for ServerNet clustering* G06.26 T0682G06^AAA OSM Service Connection Suite Required for ServerNet clustering* G06.25 *For more details, see the ServerNet Cluster Supplement for NonStop NS-Series Servers. To find out if your NonStop server supports ServerNet clustering, see the planning guide for your NonStop server. Install Node Interoperability SPRs 55

56 These SPRs facilitate software migration and software management operations between nodes running G-series RVUs and nodes running H-series and J-series RVUs: The T9621D30^ABB, T9674D30^AAM, T9276D30^AAW, and T0448G06^AAA SPRs provide the option of using a G-series RVU system to construct objects that will ultimately run on an H-series or J-series RVU system. Possible activities that can be performed in the G-series RVU system include accelerating objects that will eventually run on an H-Series or J-series RVU system. Once the objects have been properly constructed on the G-series RVU system, they can 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 Application Migration Guide. T6031G01^ABP provides the option to use DSM/SCM to manage software in an environment composed of systems running different RVU series. The systems need not be connected through Expand. 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 that have been copied to a G-series RVU system or in situations where a G-series RVU node is used to manage software for a H-series or J-series RVU system. This functionality can also be used to query the VPROC of a remote object file through Expand. Table 18 SPRs for Software Migration and Software Management Operations Between G-Series, H-Series and J-Series RVU-Based Systems Minimum SPR Product Name Description Introduced in this RVU T9617G03^AAY VPROC Required to recognize 800 files G06.27 T9621D30^ABB Binder Required to recognize OCA region G06.27 T9674D30^AAM PDTSHARE Required to recognize OCA region G06.27 T9276D30^AAW Axcel Required to recognize OCA region G06.27 T0448G06^AAA OCA Required to prepare TNS code files to run accelerated on a NonStop NS-series platform G06.27 T6031G01^ABP DSM/SCM Required to enable receiving H-series SUTs Released post G06.26 and installing and managing software on and is backwards a NonStop NS-series target system from a compatible to G NonStop S-series host (available to be Also, the G02 SPR applied to the G06.26 RVU and (installed with G06.27 compatible to G06.21). The functions in and later) meets the T6031ABP and T9298AAM are included requirements. in the G02 DSM/SCM and SWID product version updates released in G06.27 and later G-series RVUs. Back Up System Information To 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 shutting down half of $SYSTEM and other important disks, loading the RVU on the other $SYSTEM, verifying the RVU and then reviving the other $SYSTEM. Alternatively, or in addition to running your system with a mirror of $SYSTEM and loading the RVU as described, create a disk image of $SYSTEM and store it in a safe place so you can physically install and boot the backup disk if needed. For NonStop BladeSystems NB54000c, NB54000c-cg, NB56000c, and NB56000c-cg, Ensure the Core License File is Ready for Migration If you are upgrading an HP Integrity NonStop BladeSystem from a pre-j06.13 RVU to an NB54000c, NB54000c-cg (running J06.13 or later RVUs) or NB56000c or NB556000c-cg 56 Preparing to Upgrade the Server Software (Preinstallation Tasks)

57 (running J06.16 or later), you must obtain and use the CLICVAL tool. For more information, see the NonStop BladeSystem Planning Guide. If Necessary, Manually Install the NonStop Software Essentials Server Product HP recommends use of NonStop Software Essentials instead of the Planner Interface for upgrading your RVU. In addition to NonStop Software Essentials being the go-forward strategy, the Planner Interface is not supported on 64-bit NonStop system consoles. Systems running J06.13 or a later J-series RVU obtain the NonStop Software Essentials server component (T0894H02) from the SUT. If the NonStop Software Essentials server is not yet installed on your system or you want to upgrade from T0894H01 to T0894H02, you can install the latest server via SPR from Scout or use your installed NonStop Software Essentials software or the DSM/SCM Planner Interface to install the T8092H02 server. NOTE: You cannot use or run DSM/SCM with the Planner Interface to install the NonStop Software Essentials server on systems with 64-bit NonStop system consoles. If you have 64-bit NonStop system consoles only but do not have the NonStop Software Essentials server installed, you must manually install the server and the other NonStop Server Essentials software. The NonStop Software Essentials Installation and Quick Start Guide describes the procedure for manually installing the T0894H02 NonStop Software Essentials component and identifies in detail the circumstances under which manual installation of the components would need to be performed. See the NonStop Software Essentials Installation and Quick Start Guide for all of the NonStop Software Essentials server installation procedures, including the manual procedure. See the NonStop Software Essentials User s Guide for detailed information about the product. If Necessary, Manually Install the NonStop Software Essentials Server Product 57

58 6 Installing a SUT for This RVU Using NonStop Software Essentials NOTE: If you do not have NonStop Software Essentials installed, see the NonStop Software Essentials Installation and Quick Start Guide. Alerts for Installing a SUT Do not use this procedure to upgrade more than one system at a time or to install SPRs. For SPRs, see Using DSM/SCM With NonStop Software Essentials to Install SPRs (page 133). Before you install a SUT or RVU, these requirements must be met: When managing OSS files with DSM/SCM, check that the OSS Root Name Server $ZPNS is started and running on the DSM/SCM Target. (See Create a New Software Revision (page 61).) The volume where the SYSnn is being placed must be activated as $SYSTEM to install the OSS files. See the Open System Services Management and Operations Guide, or if using EasySetup, see the Open System Services Installation Guide. Save the configuration database. See Save the Current Configuration File (CONFxxyy) (page 47). Verify your system operations. See Verify System Processes (page 48). If necessary, update the system console. Obtain a user name and password authorized to use NonStop Software Essentials. See the NonStop Software Essentials User s Guide for more information about configuring which users are 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 you log 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 processes when DSM/SCM is running. The default hometerm is $ZHOME. See the NonStop Software Essentials User s Guide 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 manually using 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 46). Drain the Spooler and back up spooler control files. Receive New Software Into the Archive 1. Start TMF and DSM/SCM if they are not already running. For example: > TMFCOM START TMF > VOLUME $dsmscm_vol.zdsmscm > RUN STARTSCM 58 Installing a SUT for This RVU Using NonStop Software Essentials

59 nl startscm NOTICE: * If the hometerm chosen during INITENV, $zhome, * is not currently in a paused state, STARTSCM and DSM/SCM * server processes may hang indefinitely. 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 Manage NonStop 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. 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 files 6. 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. Receive New Software Into the Archive 59

60 11. Click Submit. The request status page appears and is updated automatically. A Status window appears and is updated automatically at regular intervals. 12. While waiting for the request to finish, check: The status of the request in the Status window. For example: EMS event messages to see if a cartridge on a non-autoloading drive of the SUT needs to be mounted. EMS messages are displayed in the EMS Events window displayed by NonStop Software Essentials when you click the system name in the System column in the table from the Status page. See the above screen shot. You can also check the Requests window to ensure that the request is finished. (Select Requests>Show Requests.) For example: 13. Expand the SUTs node in the navigation tree and monitor the request status page. When the request completes, the new SUT will appear at the top of the list of SUTs. 14. Keep NonStop Software Essentials open for the next task. 60 Installing a SUT for This RVU Using NonStop Software Essentials

61 Create a New Software Revision When you create a new software revision, NonStop Software Essentials selects the products in the SUT that are licensed for your site and replaces any previous versions of the products. The following steps assume that you are creating a new software revision that manages OSS files. If you are not, go to step 5 after you have loaded the Configuration Revisions page in NonStop Software Essentials. These instructions also assume that you have installed OSS. To configure OSS for the first time, see the Open System Services Installation Guide. For details on modifying a DSM/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 determine the 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/ :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 the target configuration. 3. Click the Modify button in the Target Maintenance group box. a. Check that the Manage OSS Files option is selected. Create a New Software Revision 61

62 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 channel drives or $SCSI for SCSI drives. If this default has been changed, then the target volume specified in NonStop Software Essentials for new subvolumes must reflect this change. 4. 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 in the 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.15 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: 62 Installing a SUT for This RVU Using NonStop Software Essentials

63 If there are any discrepancies between the set of products included in the previous configuration and the set in your new configuration, the popup shown below is displayed. (These products are removed by default from the system by DSM/SCM during the Build/Apply of the new configuration.) The dialog box lists products installed on the previous revision that are not available on the new SUT. 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 and click Continue. To include all products, click the check box in the left column header to select all the products. The New software revision list now displays the new revision level. For example: Create a New Software Revision 63

64 7. Keep NonStop Software Essentials open for the next task. Build and Apply the New Software Revision The Build process creates an activation package containing all the products listed in the new software revision. To avoid disrupting other system activities, schedule the Build to run at night and the Apply to run immediately after the build. See the NonStop Software Essentials User s Guide for information about scheduling the Build/Apply to run at different times. To build and apply the new software revision: 1. In the New software revision page, click Build/Apply to display the options for your Build/Apply. It might take several minutes for DSM/SCM to assemble the build information. During this time, the Processing New Revision progress bar is displayed. When the Build information is assembled, the Build/Apply Request page is displayed. It displays default options and assigns a name to the Build/Apply request. For example: 2. Under Perform steps, select Build, apply & process snapshot. 64 Installing a SUT for This RVU Using NonStop Software Essentials

65 3. In the Activation SYSnn: box, enter a unique number to create a new SYSnn subvolume. The value nn must be a two-digit octal number in the range %00...%77. You can issue a FILEINFO command at a TACL prompt to view the SYSnn subvolumes that are currently on your system. > fileinfo $system.*.osimage 4. Make a note of the new SYSnn. 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 RVU 5. Edit Planner instructions to operator text to provide the correct (new) SYSnn number. 6. 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 the online help for more information about Build/Apply Request options.) 7. (Optional) Confirm that the Spooler is active and not 100 percent full before executing the Build/Apply request. At a TACL prompt, start SPOOLCOM and issue a COLLECT, STATUS command. For example: 12> spoolcom $spls; collect, status COLLECT STATE FLAGS CPU PRI UNIT DATA FILE %FULL $S ACTIVE 3, $OPS0.SPL.DATA 4 8. 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 automatically updated every five seconds. For example: Build and Apply the New Software Revision 65

66 9. Check EMS messages for more detailed information about your Build/Apply. Click the system name in the System column to view EMS events on that system for this Build/Apply request. When the Build/Apply finishes successfully and a snapshot is received into the host database: The Request activity summary in the Status window shows that the Build, Apply, Create snapshot, and Receive snapshot activities finished. For example: The last message in the EMS Events window shows that the input snapshot finished successfully. The Requests window shows that the request is finished. (Select Requests> Show Requests). 10. 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: 66 Installing a SUT for This RVU Using NonStop Software Essentials

67 ============================================================================== ============================================================================== 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., 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 :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 :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 Print Operator Instructions From the Target Interface (ZPHITI) 67

68 ===========================More Targets PgDn/PgUp============================= F1-Select F15-Help F16-Return SF16-Exit Ready 4. In the Selection number field, enter the number corresponding to the logical target to which you applied the software (selection 2 in this example), and press F1 to display the Target Menu - Select Action screen. DSM Software Configuration Manager Target Menu - Select Action ============================================================================== \WARRIOR Prior snapshot :12:18:44 DEFAULT Last S/W applied on SYS 00 on :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 :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 number field, 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 operator instructions. 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 OSS command: 68 Installing a SUT for This RVU Using NonStop Software Essentials

69 Run merge_whatis if zphirnm indicates it is needed. When you finally run ZPHIRNM, the following lines are written to the log: Note: merge_whatis needs to be run to update the man pages. Files in a whatis.frag directory have changed. The merge_whatis is a shell script in /bin. It creates and updates the whatis database used by the OSS shell man, apropos, and whatis commands. You must run the merge_whatis command once against each directory that contains the man page files to be used. You will run merge_whatis after using ZPHIRNM. If you have OSS configured to run the OSS merge_whatis utility automatically, you can ignore running merge_whatis. Recovery for Problems Installing This RVU SUT or SPRs If you receive an error indication in the Requests, Status, or EMS Events windows, you might have to re-initiate the Build/Apply. See the DSM/SCM Messages Manual to determine the nature and severity of the problem. Cancel Pending Build/Apply Requests NOTE: If you inadvertently navigate away from the Status page, reopen it by clicking on the Request Name link on the Request List page. Click the Cancel button on the Request Status page. The cancel request action takes a few minutes to finish. NOTE: If you cannot cancel the Build request through NonStop Software Essentials, use the DSM/SCM Target Interface (ZPHITI) to cancel the request. See the NonStop Software and the online help for more information. Recovery for Problems Installing This RVU SUT or SPRs 69

70 7 Installing a SUT for This RVU Using the Planner Interface Alerts for Installing a SUT Do not use this procedure to upgrade more than one system at a time or to install SPRs. For SPRs, see Using DSM/SCM With the Planner Interface to Install SPRs (page 140). Before you install a SUT or RVU, these requirements must be met: When managing OSS files with DSM/SCM, check that the OSS Root Name Server $ZPNS is started and running on the DSM/SCM Target. (See Create a New Software Revision (page 74).) The volume where the SYSnn is being placed must be activated as $SYSTEM to install the OSS files. See the Open System Services Management and Operations Guide, or if using EasySetup, see the Open System Services Installation Guide. Save the configuration database. See Save the Current Configuration File (CONFxxyy) (page 47). Verify your system operations. See Verify System Processes (page 48). If necessary, update the system console. Obtain a user name and password authorized to use the DSM/SCM Planner Interface. See the DSM/SCM User s Guide for more information about configuring which users are 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 you log 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 are available only while Safeguard is running. Pause the hometerm configured for use by DSM/SCM Pathway servers and other processes when DSM/SCM is running. The default hometerm is $ZHOME. See the DSM/SCM User s Guide 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 manually using 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 46). Drain the Spooler and back up spooler control files. Receive New Software Into the Archive 1. Start TMF and DSM/SCM if they are not already running. For example: > TMFCOM START TMF > VOLUME $dsmscm_vol.zdsmscm > RUN STARTSCM startscm NOTICE: * If the hometerm chosen during INITENV, $zhome, * is not currently in a paused state, STARTSCM and DSM/SCM * server processes may hang indefinitely. Be sure this * hometerm has been paused! 70 Installing a SUT for This RVU Using the Planner Interface

71 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/SCM Archive. 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 71

72 9. From the list, select the tape drive that contains the SUT, and click OK. The Request Source Options dialog box closes. 10. In the Options group box of the Receive Software Request dialog box, click Scheduling. The Request Scheduling Options dialog box appears. Make the appropriate selections and click OK. The Request Scheduling Options dialog box closes. 11. In the Receive Software Request dialog box, click OK. A Status window appears and is updated automatically at regular intervals. 12. While waiting for the request to finish, check: The status of the request in the Status window. For example: 72 Installing a SUT for This RVU Using the Planner Interface

73 EMS event messages to see if a cartridge on a nonautoloading drive of the SUT needs to be mounted. EMS messages are displayed in these windows: The EMS Event Stream window The EMS Events window displayed by DSM/SCM when you click Show EMS events from the Status window You can also check the Requests window to ensure that the request is finished. (Select Requests>Requests list.) For example: Receive New Software Into the Archive 73

74 13. When the request is finished, close the Status and Requests windows. 14. Update the Software in Archive dialog box to show the newly received SUT. Select Window>Refresh. The new SUT appears in the window. 15. Keep the Planner Interface open for the next task. Create a New Software Revision When you create a new software revision, DSM/SCM selects the products in the SUT that are licensed for your site and replaces any previous versions of the products. 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 determine the 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/ :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 target configuration. 2. Select Maintain Target Maintenance Modify. a. Check that the Manage OSS Files option is selected. 74 Installing a SUT for This RVU Using the Planner Interface

75 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 channel drives or $SCSI for SCSI drives. If this default has been changed, then the target volume specified in the Planner Interface for new subvolumes must reflect this change. d. 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 last software revision that was built for the target system. It might take several minutes for the dialog 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.15 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 75

76 6. Click Continue when the Confirmation message appears: If there are any discrepancies between the set of products included in the previous configuration and the set in your new configuration, a warning message appears listing any products missing in the current configuration that were present in the previous configuration. (These products are removed from the system by DSM/SCM during the Build/Apply of the new configuration.) You might receive a warning that certain OSS products are not DSM/SCM enabled. If this is the case, install them using PINSTALL/COPYOSS. See the appropriate OSS manuals for using PINSTALL and COPYOSS. The Non SUT Products screen might appear: The dialog box lists products installed on the previous revision that are not available on the new 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: 76 Installing a SUT for This RVU Using the Planner Interface

77 7. Keep the Planner Interface open for the next task. Build and Apply the New Software Revision The Build process creates an activation package containing all the products listed in the new software revision. To avoid disrupting other system activity, schedule the Build to run at night and the Apply to run immediately after the build. See the DSM/SCM User s Guide for information about scheduling the Build/Apply to run at different times. To build and apply the new software revision: 1. In the New software revision dialog box, click Build/Apply to display the options for your Build/Apply. It might take several minutes for DSM/SCM to assemble the build information. During this time, the Build/Apply Request dialog box 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 77

78 2. Under Perform steps, select Build, apply & process snapshot. 3. In the Activation SYSnn: box, enter a unique number to create a new SYSnn subvolume. The value nn must be a two-digit octal number in the range %00...%77. You can issue a FILEINFO command at a TACL prompt to view the SYSnn subvolumes that are currently on your system. > fileinfo $system.*.osimage 4. Make a note of the new SYSnn. 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 RVU 5. Click Edit instructions to display the Planner Instructions dialog box. 6. Edit the instructions to provide the correct (new) SYSnn number, and then click OK. The Planner Instructions box closes. 7. 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 help for more information about Build/Apply Request options.) When completed, click OK. 78 Installing a SUT for This RVU Using the Planner Interface

79 8. (Optional) Confirm that the Spooler is active and not 100 percent full before executing the Build/Apply request. At a TACL prompt, start SPOOLCOM and issue a COLLECT, STATUS command. For example: 12> spoolcom $spls; collect, status COLLECT STATE FLAGS CPU PRI UNIT DATA FILE %FULL $S ACTIVE 3, $OPS0.SPL.DATA 4 9. In the Build/Apply Request dialog box, click OK. Build and Apply the New Software Revision 79

80 DSM/SCM runs the Build and Apply steps and displays a Status window, which is automatically updated at regular intervals. For example: 80 Installing a SUT for This RVU Using the Planner Interface

81 10. Check EMS messages for more detailed information about your Build/Apply: a. In the Events window, click Refresh to see newer messages. b. When finished viewing, click Close. NOTE: If you encounter any problems, see the DSM/SCM User s Guide or online help. When the Build/Apply finishes successfully and a snapshot is received into the host database: The Request activity summary in the Status window shows that the Build, Apply, Create snapshot, and Receive snapshot activities finished. For example: Build and Apply the New Software Revision 81

82 The last message in the EMS Events window shows that the input snapshot finished successfully. The Requests window shows that the request is finished. (Select Requests> Requests list). 11. Close the EMS Events, Status, and Request windows. 12. Exit the DSM/SCM Planner Interface. Print Operator Instructions From the Target Interface (ZPHITI) Print the operator instructions that you edited. 1. 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 11NOV Installing a SUT for This RVU Using the Planner Interface

83 (c) Hewlett Packard Development Company L.P., All Rights Reserved ============================================================================== F1-Logon F8-Clear entry F15-Help SF16-Exit Ready 2. Enter your user ID or alias (if necessary) and password and press F1 to log on to the Target Interface. The Main Menu appears: DSM Software Configuration Manager Main Menu ============================================================================== \WARRIOR Prior snapshot :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 :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 ===========================More Targets PgDn/PgUp============================= F1-Select F15-Help F16-Return SF16-Exit Ready 4. In the Selection number field, enter the number corresponding to the logical target to which you applied the software (selection 2 in this example), and press F1 to display the Target Menu - Select Action screen. Print Operator Instructions From the Target Interface (ZPHITI) 83

84 DSM Software Configuration Manager Target Menu - Select Action ============================================================================== \WARRIOR Prior snapshot :12:18:44 DEFAULT Last S/W applied on SYS 00 on :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 :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 number field, 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 operator instructions. 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 OSS command: Run merge_whatis if zphirnm indicates it is needed. When you finally run ZPHIRNM, the following lines are written to the log: Note: merge_whatis needs to be run to update the man pages. Files in a whatis.frag directory have changed. The merge_whatis is a shell script in /bin. It creates and updates the whatis database used by the OSS shell man, apropos, and whatis commands. You must run the merge_whatis command once against each directory that contains the man page files to be used. 84 Installing a SUT for This RVU Using the Planner Interface

85 You will run merge_whatis after using ZPHIRNM. If you have OSS configured to run the OSS merge_whatis utility automatically, you can ignore running merge_whatis. Recovery for Problems Installing This RVU SUT or SPRs If you receive an error indication in the Requests, Status, or EMS Events windows, you might have to re-initiate the Build/Apply. See the DSM/SCM Messages Manual to determine the nature and severity of the problem. Cancel Pending Build/Apply Requests NOTE: If you inadvertently close the Status dialog box, reopen it by selecting Requests Requests list and then double-clicking the request. 1. 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, use the DSM/SCM Target Interface (ZPHITI) to cancel the request. See the DSM/SCM User s Guide and online help. Recovery for Problems Installing This RVU SUT or SPRs 85

86 8 Running ZPHIRNM Alerts During the Build/Apply phase, DSM/SCM places product files in their subvolumes with temporary (fabricated) file names so that new file names do not conflict with the file names of currently running programs. This chapter describes how to run the ZPHIRNM program on the target system to: Rename the files that currently have actual file names with fabricated names. These files become obsolete when the new files are renamed. 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 it exists 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 compared to the last configuration activated). If none of the ZcccGP files change, ZMODGP is not run. 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 running ZPHIRNM. You must have rename (purge) access to all files being renamed. Run ZPHIRNM as the super ID (255,255). If you are connected to an Expand network, you might see a message stating that the NonStop SQL file, ZZSQLCI2, was not renamed during ZPHIRNM. However, on further examination of the log file, you might find that ZPHIRNM did finally rename the file, in which case you can ignore the error message and continue. If you are using DSM/SCM to manage OSS files, ZPHIRNM notifies you if and when to run the 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 errors in the new and changed files will not be discovered in preview or trial mode because ZPHIRNM in preview mode does not actually rename the files. Therefore, ZMODGP will not be run against 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. See Hotstuff 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 86 Running ZPHIRNM

87 DNSCACHE DNSHOSTS DNSLOCAL DNSREV DNREVBAK HOSTS NETWORKS PORTCONF PROTOCOL RESCONF SERVICES SMTPCONF The file names of NonStop TCP/IPv6 that reside on the SUT are: ztcpip.smplhost ztcpip.smplprot ztcpip.smplnetw ztcpip.smplport ztcpip.smplresc ztcpip.smplserv Stop Applications Before running ZPHIRNM: 1. Stop DSM/SCM if it is still running. For example: > VOLUME $dsmscm_vol.zdsmscm > Run STOPSCM STOP CNFGINFO server process $ZPHC STOP DSM/SCM Pathway system $YPHI PATHCOM $YPHI;SHUTDOWN!,WAIT $Z02H: TCP TCP-H, STOPPED $Z02H: TCP TCP-T, STOPPED STOP DSM/SCM Alternate EMS Collector $ZPHI where $dsmscm_vol is the DSM/SCM volume. 2. Perform steps 1 through 4 of the procedure for performing an RVU upgrade on a node in the NonStop BladeCluster Solution Manual. 3. 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 87

88 1. Use the SPOOLCOM;COLLECT $collector-process, LISTOPENS command to identify processes that currently have jobs open. 2. Use the SPOOLCOM;JOB (STATE PRINT) command to determine which jobs are currently printing. Take the appropriate action to ensure that these jobs either terminate when finished or are stopped. After receiving the SPOOLER DRAIN command, the supervisor stops accepting jobs for collection or printing (new opens are rejected with a file-system error 66 device downed). Each collector stops when it has no more open jobs. Each print process finishes printing active jobs and then stops. After all collectors and print processes have stopped, the supervisor process stops itself. The Spooler enters the dormant state, ready to be warm started. CAUTION: Never use the TACL STOP command to halt the Spooler. The control file can be corrupted during the next warm start or rebuild. For more information on draining the Spooler, see Support Note S99086, NSK Spooler Migration and Draining Instructions and in the Spooler Utilities Reference Manual. Back Up the Spooler Control Files ZPHIRNM While the spooler environment is closed, back up the spooler control files to render a known database from which you recover in case of a catastrophic spooler failure. Make sure that you drain the Spooler: BACKUP/OUT SPLBKUP/$TAPE,($SYSTEM.SPOOLER.*,$DATA01.SPOOLER.DATA),LISTALL During 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 currently running programs. The ZPHIRNM program renames files that currently have actual file names with fabricated names and renames new files, which have fabricated names, with their actual names. ZPHIRNM is run from the DSM/SCM subvolume. Using ZPHIRNM PREVIEW Mode You can do a preview run of ZPHIRNM to check that the target subvolumes (TSVs) and associated map files are consistent. Running ZPHIRNM in PREVIEW mode simulates the ZPHIRNM process without actually updating files or activating the configuration. In PREVIEW mode, ZPHIRNM indicates whether TMF needs to be up when running ZPHIRNM. For example, if no SQL program files need running, 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 files will be named ZFBccncc, but cannot be easily distinguished from non-zcccgp files also named ZFBccncc. Example of ZPHIRNM: Statistics: 88 Running ZPHIRNM TSVs: TSVs in new configuration TSVs in old configuration TSVs in new configuration only... 0 TSVs in old configuration only... 1 TSVs shared by new and old configurations TSVs processed in new config TSVs processed in old config (obsolete)... 1

89 Files Processed: Files processed in new configuration Files processed in new configuration only... 0 Files processed in old configuration only... 9 Files processed that are shared by new and old configuration Files processed & unchanged between new and old configuration Files processed in obsolete TSVs Files renamed from real name to fabricated name 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 Total Number of files renamed Number of files renamed back during undo processing... 0 Generic Process MODification(ZMODGP) is not required because no ZcccGP files in 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 errors are 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 information about PREVIEW mode. For more information, see the NonStop Software Essentials User s Guide. Steps for Running ZPHIRNM 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 subvolume to which you just applied software. The SYSnn subvolume must 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 ZPHIRNM 89

90 Do you want to use a log file with this session? (Y/N): y You may use any file for logging. If you request to use a disk file that doesn't exist, it will be created as an edit file. Please enter a filename: elist00 Log file is open, Zphirnm will now begin processing. ZPHIRNM begins processing and provides status of its progress. 4. If necessary, you can compare the creation dates of the whatis file to the whatis_old file to see if changes occurred: a. Run the more command against the whatis file: more /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 Successfully 1. 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 the subvolume it is currently processing to its original state. A nonfatal error is one that affects processing 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 message and 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/SCM Messages Manual for a complete list of ZPHIRNM messages. 90 Running ZPHIRNM

91 9 Loading This RVU This chapter describes how to perform a system load on this RVU into the memory of each processor in a NonStop system. NOTE: For additional information about performing a system load of a NonStop system, see the NonStop Operations Guide. By default, one $SYSTEM is already configured. You can select $SYSTEM, FCDM-Load, CLIM-Attached-Load, or an alternate system volume: The $SYSTEM disks must contain the current RVU operating system files for the NonStop system. Table 19 (page 91) and Table 20 (page 91) identifies the possible load paths you would use to perform an FCDM-Load and a CLIM-Attached-Load, respectively. Table 19 System Load Paths in Order of Use for FCDM-Load Load Path Description Data Travels From To Processor Over ServerNet Fabric 1 Primary $SYSTEM-P 0 X 2 Primary $SYSTEM-P 0 Y 3 Backup $SYSTEM-B 0 X 4 Backup $SYSTEM-B 0 Y 5 Mirror $SYSTEM-M 0 X 6 Mirror $SYSTEM-M 0 Y 7 Mirror backup $SYSTEM-MB 0 X 8 Mirror backup $SYSTEM-MB 0 Y 9 Primary $SYSTEM-P 1 X 10 Primary $SYSTEM-P 1 Y 11 Backup $SYSTEM-B 1 X 12 Backup $SYSTEM-B 1 Y 13 Mirror $SYSTEM-M 1 X 14 Mirror $SYSTEM-M 1 Y 15 Mirror backup $SYSTEM-MB 1 X 16 Mirror backup $SYSTEM-MB 1 Y Table 20 System Load Paths in Order of Use for CLIM-Attached-Load Load Path Description Data Travels From To Processor Over ServerNet Fabric 1 Primary $SYSTEM-P 0 X 2 Primary $SYSTEM-P 0 Y 3 Backup $SYSTEM-B 0 Y 4 Backup $SYSTEM-B 0 X 5 Mirror $SYSTEM-M 0 X 6 Mirror $SYSTEM-M 0 Y 7 Mirror backup $SYSTEM-MB 0 Y 8 Mirror backup $SYSTEM-MB 0 X 91

92 Table 20 System Load Paths in Order of Use for CLIM-Attached-Load (continued) Load Path Description Data Travels From To Processor Over ServerNet Fabric 9 Primary $SYSTEM-P 1 Y 10 Primary $SYSTEM-P 1 X 11 Backup $SYSTEM-B 1 X 12 Backup $SYSTEM-B 1 Y 13 Mirror $SYSTEM-M 1 Y 14 Mirror $SYSTEM-M 1 X 15 Mirror backup $SYSTEM-MB 1 X 16 Mirror backup $SYSTEM-MB 1 Y A CLIM-Attached-Load attempts to load the system from a system disk in the NonStop Storage CLIMs connected to a ServerNet switch. CLIM-Attached-Load for system with 2 CLIMs over $SYSTEM: ServerNet Switch Path Group Module Slot Connector Fiber Primary LUN Mirror LUN Primary N/A Backup N/A Mirror N/A 201 Mirror Backup N/A 201 CLIM-Attached-Load for a system with four CLIMs over $SYSTEM: ServerNet Switch Path Group Module Slot Connector Fiber Primary LUN Mirror LUN Primary N/A Backup N/A Mirror N/A 101 Mirror Backup N/A 101 An FCDM-Load attempts to load the system from a system disk in the disk drive enclosure connected to IOAM enclosure group 110: IOAM FCSA Disk Drive Enclosure Path Group Module Slot SAC Shelf Bay Primary Backup Mirror Mirror Backup Loading This RVU

93 You can configure additional alternate system disks. To create an alternate system disk, contact your HP authorized service provider to perform the task. Then use OSM to make the disk available in the Configuration drop-down menu in the System Load dialog box. The alternative system disks are displayed in the Attributes tab under the System object in the OSM Service Connection and are also displayed in the OSM Low-Level Link System Load dialog box in the Configuration shortcut menu. Alerts Before 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 stopping applications, devices, and processes. Ensure that sufficient swap file space is available for the installation. Either use NSKCOM to ensure 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 attempt to close the dialog box, a message dialog box appears notifying you that the system startup process 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 normal operation. If you must stop the system startup process, click Abort. (The abort process should take effect within 30 seconds.) In the System Load dialog box, either select all four disk paths, or check that the selected disk path is correct. If you do not select all four or select the incorrect disk path, the system does not load properly. If you have problems performing a system load, see the NonStop Operations Guide, Chapter 15. Perform Updates 1. Before Halting the Processors Before halting the processors on your system, perform these actions as needed. Perform Required RVU-Specific Upgrades When Upgrading From J06.04 or an Earlier RVU: Removing #ZPLS When upgrading to this RVU from J06.04 or an earlier RVU, before halting the processors, you must remove the SERVER #ZPLS entry from the OSS subsystem maintenance file OSSINFIL on all systems with OSS installed. The simplest way to do this is to use the TEDIT utility to change the SERVER #ZPLS entry to a comment, as follows: TEDIT $SYSTEM.ZOSSINS.OSSINFIL Alerts 93

94 Then change SERVER #ZPLS to * SERVER #ZPLS Failure to do this can result in an error during startup of OSS. This error occurs on systems with pre-t0585h01. When Upgrading From J06.05 or an Earlier J-Series RVU: CLIM Software CLIMs configured with the CLIM software released with J06.05 or J06.04 are not compatible with J06.06 and later RVUs. Performing the CLIM upgrade when the processors are halted, as described in 6. Upgrade the CLIM Software (page 98), 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 the RVU upgrade. Preliminary online CLIM upgrades are only supported for J06.06 and later J-series RVUs. If You Are Migrating to a Another NonStop System If, as part of your migration to the new RVU, you are also migrating your current NonStop system to a new NonStop system, make sure your HP authorized service provider has fully completed the new system installation and that the new system is powered on. Determine If the System Firmware Version Will Need to Be Upgraded Before you halt the processors on your system as described in 2. Halt the Processors (page 96), find out if your system firmware will need to be updated as you prepare load to load the new RVU. System firmware would be updated when: You are migrating your current NonStop system to another NonStop system from which to load and run the new RVU. However, you cannot definitively identify the new system firmware version until the new system has been fully installed and powered on. NB50000c or NB50000c-cg to NB54000c or NB54000c-cg NS2000 series to NS2200 series You receive a support note or Hotstuff message instructing you to update your HSS firmware. Unless you are migrating to a new system that has not yet been fully installed, you should take this opportunity to identify the latest supported system firmware versions for your system and determine which system firmware version is currently installed on your system. 1. See these chapters in the latest edition of the NonStop Firmware Matrices: The chapter Valid System Firmware and HSS Combinations identifies the server firmware bundle versions (which contains the system firmware and ilo firmware) and the HSS firmware versions released on the most recent System Firmware Dates by system and processor type. NOTE: The Server Firmware Bundle Version of the system firmware version must be compatible with (in the same table row with) the HSS firmware SPR Revision for your system. The chapter Identification of BL860c i4, BL860c i2, and rx2800 Server Firmware Versions identifies, by processor-specific firmware bundle version number, the system 94 Loading This RVU

95 firmware versions and ilo firmware versions that are currently supported and those that are not. 2. If the blade elements that will be used with the new RVU are already installed, identify the system firmware version currently installed on each of them. The system firmware version, which is stored on the system board of each blade element, is identified as follows: NOTE: If necessary, contact your HP authorized service provider for assistance with these procedures: On NonStop BladeSystems, invoke ilo from the OSM Service Connection. The ilo is displayed from a browser, from which you select Firmware Versions to display the current system firmware version. On NS2x00 systems other than the NS2000 series, obtain the ilo IP from the DHCP Server list of IPs and invoke it manually by opening a browser and entering the IP. On NS2000 series systems, the system firmware is stored and loaded from the DVD drive in each blade element. 3. If your currently-installed system firmware version is no longer supported, perform a system firmware update as described in 3. (Conditional): Update the System Firmware (page 96). 4. If the currently-installed system firmware version is supported, you do not need to perform a system firmware update. Determine If the HSS Firmware Version Will Need to Be Upgraded Before you halt the processors on your system as described in 2. Halt the Processors (page 96), find out if your HSS firmware will need to be updated as you prepare to load the new RVU. HSS firmware would need to be updated when: You are migrating your current NonStop system to another NonStop system to run the new RVU. However, you cannot definitively identify the new HSS firmware version until the new system has been fully installed and powered on. NB50000c or NB50000c-cg to NB54000c or NB54000c-cg NS2000 series to NS2200 series You receive a support note or Hotstuff message instructing you to update your HSS firmware. Unless you are migrating to a new system that has not yet been fully installed, you should take this opportunity to identify the latest supported HSS firmware versions for your system and determine which HSS firmware version is currently installed on your system. 1. Identify the supported HSS firmware version(s) for your system by referring to the chapter Valid System Firmware and HSS Combinations in the latest edition of the NonStop Firmware Matrices. This chapter identifies both the server firmware bundle versions and the HSS firmware versions released on the most recent System Firmware Dates by system and processor type. NOTE: The Server Firmware Bundle Version of the system firmware version must be compatible with (in the same table row with) the HSS firmware SPR Revision for your system. 2. Identify the HSS firmware version that is currently installed on your system s blade elements. On all J-series systems, you identify the current HSS firmware version installed on each blade element by using the OSM Service Connection. The OSM Low-Level Link also displays the current HSS firmware version on the Update HSS screen. For detailed instructions, see Verify Halted State Services (HSS) in the NonStop System Console Installer Guide. If necessary, contact your HP authorized service provider for assistance with these procedures. Perform Updates 95

96 3. If your currently-installed HSS firmware version is no longer supported, perform a system firmware update as described in 4. (Conditional): Update the HSS Firmware (page 96). 4. If your currently-installed HSS firmware is supported, you do not need to perform an HSS firmware update. 2. Halt the Processors You must halt the processors whenever you migrate your host system from one RVU to another. Perform these steps: 1. Log on to the OSM Low-Level Link. 2. 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. (Conditional): Update the System Firmware To update your system firmware: 1. Identify the system firmware version that is currently installed on your system and determine whether or not it needs to be updated for the new RVU as described in Determine If the System Firmware Version Will Need to Be Upgraded (page 94). 2. If the system firmware currently installed on your system does not need to be updated, skip this section and proceed to 4. (Conditional): Update the HSS Firmware (page 96). 3. If the system firmware version needs to be updated, see the chapter Supplementary Steps for Updating Firmware Components Not Delivered on the SUT in the latest edition of the NonStop Firmware Matrices. In the following table, the rightmost column identifies the name of the NonStop Firmware Matrices section that contains the firmware update instructions for the system types identified in the leftmost column. For firmware update instructions for these NonStop systems.. NS2100, NS2200, NS2200T, NS2200ST NB54000c and NB54000c-cg NB56000c and NB56000c-cg Refer to the procedures in this section.. Updating rx2800 i2 Blade System Firmware Updating BL860c i2 Blade System Firmware Updating BL860c i4 Blade Systems Firmware 4. (Conditional): Update the HSS Firmware Updating the HSS Firmware on All J-Series Systems Except NS2000 Series Make sure that the HSS firmware version on your J-series system needs to be updated as described in Determine If the HSS Firmware Version Will Need to Be Upgraded (page 95). To upgrade the HSS firmware, perform these tasks and refer to the NonStop System Console Installer Guide for the detailed instructions: 1. Uninstall the previous version of HSS firmware. 2. Install the new HSS firmware. 3. After downloading the new HSS firmware version, use OSM Low-Level Link to perform the Update HSS action to create the system serial number-specific HSS file from which the processors will boot. Upon successful completion of the action, OSM performs a Hard Reset so that when loaded, the processors will be running the new version of HSS firmware. 96 Loading This RVU

97 NOTE: Prior to NonStop System Console Installer DVD, Update 18, authentication failures could occur when using certain OSM actions, including Update HSS action in OSM Low-Level Link. This problem is automatically fixed when you run the Master Installer on NonStop System Console Installer DVD, Update 18 or later. See Support Note SN for a workaround option if you do not have the Update 18 or later DVD. Updating HSS Firmware on NS2000 Series System Blade Elements To update the HSS firmware on each blade element in an NS2000 series system: 1. Make sure the HSS firmware on the blade element needs to be updated as described in Determine If the HSS Firmware Version Will Need to Be Upgraded (page 95). If it does, obtain the latest HSS BOOT CD. 2. Make sure the blade element is powered on. 3. Wait until the DVD LED on the front panel of the blade element turns green, then push the DVD eject button on the DVD drive. 4. Verify that the latest HSS BOOT CD is installed in the DVD drive tray. Insert the CD if it is not in the tray and gently push the tray to close it. NOTE: Close the DVD tray immediately after verifying or inserting the correct HSS Boot CD. If the tray is left open for more than one or two minutes, the CD is not detected and the processors are not loaded when the server is started. If this situation occurs, contact your HP authorized service provider for assistance. 5. Perform a power cycle on each of the affected blade elements to load the new HSS firmware from the CD. NOTE: Keep the HSS BOOT CD in the DVD drive until the next HSS BOOT CD update is required and the CD is replaced. The HSS BOOT CD cannot be powered off and then powered back on. 5. (Required Only for Upgrade from J06.13 or Earlier to J06.14 or Later) Perform a Hard Reset This procedure is necessary if you are migrating from J06.13 or an earlier J-series RVU to J06.14 or a later J-series RVU, but only if you did not already perform one of these two actions: A power cycle after updating system firmware through HP SUM as described in 3. (Conditional): Update the System Firmware (page 96). A Hard Reset as part of the HSS firmware update action performed from the OSM Low-Level Link in Updating the HSS Firmware on All J-Series Systems Except NS2000 Series (page 96). To perform a Hard Reset: 1. Logon 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. Perform Updates 97

98 6. Upgrade the CLIM Software If you have not upgraded the CLIMs online before performing this RVU upgrade, upgrade the CLIM software on each CLIM now. See Managing CLIM Firmware and Software (page 29). 7. (Optional) Update the CLIM Firmware If your system has CLIMs attached, it is important that your CLIM firmware be compatible with your system. Refer to the NonStop Firmware Matrices to make sure you have compatible firmware levels for all CLIM components. For instructions on upgrading CLIM firmware when a system is halted and when it is running, see the Cluster I/O Protocols (CIP) Configuration and Management Manual. If CLIM firmware does need to be updated and you are using the down system method, see Managing CLIM Firmware and Software (page 29) for instructions. Perform the CLIM firmware update now. 8. Loading the System If the automatic system load is not successful using one load path, the system load task attempts to use another path and keeps trying until all possible paths have been used or the system load is successful. Eight paths are available for loading. The CIIN file is automatically invoked after the first processor is loaded. The CIIN file contains the TACL RELOAD * command, which loads the remaining processors. For details on load paths, see the hardware installation manual for your system. Steps for Loading the System A normal system load consists of loading the operating system from disk into the memory of processor 0 or processor 1 (this assumes the default location is the $SYSTEM volume): 1. In the OSM Low-Level Link, select Start System. The System Load dialog box appears. 2. a. From the Configuration drop-down menu under System Load Configuration, select a system load volume. You can select the $SYSTEM, FCDM-Load, CLIM-Attached-Load, or an alternate system volume. b. 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 Disk Configuration dialog boxes as needed. 3. In the SYSnn box, enter nn, which is the number of the system subvolume that contains the version of the operating system you will load, the version created by DSM/SCM. a. Under Configuration File, select Current (CONFIG), the default configuration file that represents the configuration currently running. b. Under SYSnn and CIIN Option, verify that the CIIN Disabled option is not selected. The CIIN file must be enabled because it contains commands needed to start the server. 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. 4. Under Configuration, ensure that all the check boxes for all paths are selected. 98 Loading This RVU

99 5. Click Start System. The system load begins. If you want to stop the load process, click Abort in the System Load dialog box. You might wait up to 30 seconds before the abort takes effect. CAUTION: Do not close the System Load dialog box while startup is in progress. If you attempt to close the dialog box, an OSM message box indicates that the system startup process will be stopped if you continue. If you stop a system startup before the operation finishes, the state of your system cannot be predicted. You might need to perform another system startup to enable the system to resume normal operation. The Details dialog box displays Logon successful and Read configurations passed (FCDM example): The following example shows the same dialog box for a CLIM-attached load: Perform Updates 99

100 Start the MR-Win6530 terminal emulator and open one window each for the CNSL session display and the CLCI session display. If one or more of the startup event stream windows or startup TACL windows does not launch on the system console after a few minutes (5 to 8 minutes), abort system startup, close the OSM Low-Level Link, reboot the system console, and restart the system load using the OSM Low-Level Link again. 6. Monitor the system startup process. Messages indicating the progress and completion of the system load, and the reload of processors indicated in the CIIN file, appear in these display locations on the system console. When the system load is complete (the operating system is loaded successfully into the memory of 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 on System Startup dialog box. For recovery procedures, see the Processor Halt Codes Manual or Operator Messages Manual. 100 Loading This RVU

101 Completing the System Load (If Necessary) Loading the processors with the CIIN file is usually automatic. However, if the operating system loaded successfully into processor 0 or processor 1, but the commands in the CIIN file do not reload all remaining processors, use the RELOAD TACL commands. You must be super ID (255,nnn) to load the processors. 1. From the system console, log on to the system as a super-group user (255,nnn) and enter: > RELOAD *, PRIME 2. 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 the system console screen: PROCESSOR RELOAD: nn For complete syntax, considerations, and examples of the TACL RELOAD command, see the TACL Reference Manual. Verifying That the System Is Started Verify 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. Perform Updates 101

102 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, the update procedures may vary based on the system type. See the documentation specific to your 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 applicable to your system. See the NonStop Firmware Matrices document for the minimum required version 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 applicable to your system SWAN/SWAN2 Concentrator firmware SS7 controller firmware, if applicable to your system CLIM firmware, if your system has CLIMs attached. Update CLIM and CLIM component firmware, if needed. See Managing CLIM Firmware and Software (page 29). Prepare the Down System CLIM Tool or the Down System CLIM Firmware Upgrade action on the OSM Service Connection. Update the firmware for CLIM components as needed. See Managing CLIM Firmware and Software (page 29) and the CLuster I/O Module (CLIM) Software Compatibility Reference for details. See Chapter 2: Managing Microcode and Firmware for a description of the firmware installation procedure. To find out what firmware is required for your system, see the appropriate planning guide. After the System Load After performing the system load as described in 8. Loading the System (page 98), perform steps 6 through 9 from the procedure for performing an RVU upgrade on a node in the NonStop BladeCluster Solution Manual. 102 Loading This RVU

103 10 Resuming Normal Operations Revive the Down Half of the Mirrored Disk If you shut down half of $SYSTEM and other mirrored disks before applying the new RVU, revive the disks now. For instructions on how to bring up the downed half of a mirrored disk, see the Guardian User's Guide. Your Core License For NB54000c and NB5400c-cg systems, use the OSM Read Core License action and verify that the license information is correct for your system. See the NonStop BladeSystem Planning Guide for more information. Start System Applications You can now start your application software. Follow your site s procedures for executing the system configuration and startup (command) files to accomplish this. DSM/SCM is often started automatically by a system command file. If not, you must start it manually as described next. Before Starting DSM/SCM Initialize SQL for NonStop SQL/MP NOTE: ZZSQLCI2 is a temporary file that contains the SQLCI2 program. SQLCI2 is the process through which the NonStop SQL/MP conversational interface (SQLCI) communicates with the NonStop SQL/MP executor to request various functions. After SQL initialization is complete, 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. If you cannot find a copy of ZZSQLCI2 on the $SYSTEM disk, use DSM/SCM to export the file from 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 information on exporting the file from the Archive, see NonStop Software Essentials online help. 1. 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. NOTE: Although NonStop SQL/MP requires that you initialize SQL before you start DSM/SCM, NonStop SQL/MX does not require this step. For information about installing NonStop SQL/MX, see the SQL/MX Release 3.2 Installation and Upgrade Guide. Enter: > SQLCI INITIALIZE SQL; EXIT; 4. Copy the ZZSQLCI2 file saved previously back to the $SYSTEM disk. For example: Revive the Down Half of the Mirrored Disk 103

104 > FUP DUP $SYSTEM.BKUPZSQL.ZZSQLCI2, $SYSTEM.SYSTEM.*, SAVEALL Cold Start the Pathway Configuration 1. 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/SCM 1. From the ZDSMSCM subvolume, start DSM/SCM: > RUN STARTSCM Because the $ZHOME reliable home-term process is not an interactive process and is always paused, no action is necessary. 2. Press Enter. STARTSCM automatically runs the IP6031 TACL macro. This step can take several minutes. Run merge_whatis After coldloading the system, you might need to run the OSS merge_whatis command. (ZPHIRNM notifies you if you need to run it.) (The merge_whatis command is a shell script in /bin that creates and updates the whatis database used by the OSS shell man, apropos, and whatis commands.) You might have a shell script that runs the following, depending on your OSS environment: /bin/merge_whatis NOTE: You can run the Pcleanup utility on any file that is managed and audited by DSM/SCM before running the merge_whatis command. However, the OSS utility, Pcleanup cleans up OSS files, but not DSM/SCM files, in the OSS file system. Only the DSM/SCM CLEANOSS macro cleans up DSM/SCM files in the OSS file system. The CLEANOSS macro is run only if you fall back and then migrate again to a new PVU. During a Build/Apply, DSM/SCM automatically prompts 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 104 Resuming Normal Operations

105 cat1 cat4 cat7 whatis.frag cat2 cat5 cat8 whatis_old cat3 cat6 whatis /usr/share/man: After you run merge_whatis, the directory contains a file named whatis, containing the database. If you have previously installed OSS, a file named whatis_old is present, containing the previous version of the database. Configure Specific Products (Post-System Load) This section contains information about the configuration of various products such as OSS and SMF. 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.ZTCPIP subvolume. Otherwise, applications dependent on proper network connections will fail. Alerts: See Back Up (Copy) Files in the $SYSTEM.ZTCPIP Subvolume (Best Practice) (page 86). 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/IP configuration files in your $SYSTEM.ZTCPIP subvolume: HOSTS PROTOCOL NETWORKS PORTCONF RESCONF SERVICES Perform a FUP DUP operation to rename the sample configuration files from this RVU SUT to the real 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 insert previous network port information into each individually copied file. The sample configuration files are named: SMPLHOST SMPLPROT SMPLNETW SMPLPORT SMPLRESC SMPLSERV Configure Specific Products (Post-System Load) 105

106 To 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 >FUP DUP $SYSTEM.ZTCPIP.SMPLPORT, $SYSTEM.ZTCPIP.PORTCONF >FUP DUP $SYSTEM.ZTCPIP.SMPLRESC, $SYSTEM.ZTCPIP.RESCONF >FUP DUP $SYSTEM.ZTCPIP.SMPLSERV, $SYSTEM.ZTCPIP.SERVICES Step 2: Check the PROTOCOL File (Optional) CAUTION: For both CIP and NonStop TCP/IPv6 (even if running in IPv4 mode), you must make sure that the PROTOCOL file contains ipv6 and icmpv6 entries. If these entries are absent, a network failure might occur because the new socket routines present in TELSERV, LISTNER, and FTP access the entries in the PROTOCOL file. If the PROTOCOL configuration file exists in $SYSTEM.ZTCPIP, you must add two lines from the sample PROTOCOL file (SMPLPROT). Find the lines in SMPLPROT from the SUT that refer to IPV6 and ICMPV6 and copy those lines into your $SYSTEM.ZTCPIP.PROTOCOL file. For example: 12> TYPE SMPLPROT # 1.1 Tandem # # Internet (IP) protocols # This file is never consulted when the yellow pages are running # ip 0 IP # internet protocol, pseudo protocol number icmp 1 ICMP internet control message protocol ggp 3 GGP gateway-gateway protocol tcp 6 TCP transmission control protocol pup 12 PUP PARC universal packet protocol udp 17 UDP user datagram protocol ipv6 41 IP internet protocol for v6 icmpv6 58 ICMP internet control message protocol for v6 Step 3: Optional: For Planner Interface, Ensure That PORTCONF and SERVICES Files Are Complete The PORTCONF file specifies the ports that the LISTNER process listens to and the corresponding server program it invokes when the request comes in. If you copied files as documented in Step 1, for the DSM/SCM Planner Interface to work, you must add a services line corresponding to DSM/SCM in the PORTCONF file (shown in bold lettering) and save the file. If you did not copy the files as documented in Step 1, no action is necessary. An example of the PORTCONF file: 58> type portconf # # This file tells the listner program which ports to # listen to, and what programs to run # Telnet is directly, and does not use the listner's # services. # To run the listner use: # $system.ztcpip.listner / name.../ [config-file-name] # where config-file-name is this file. # ftp $system.ztcpip.ftpserv finger $system.ztcpip.fingserv 7 $system.ztcpip.echoserv 106 Resuming Normal Operations

107 phiwsock $dsmscm.zdsmscm.pdpexe Applications use the SERVICES file to retrieve the service port numbers and service names. If you copied files as documented in Step 1, check that the last lines of the SERVICES file have an entry similar to: phiwsock 1089/tcp #DSM/SCM Planner Interface For DSM/SCM, the port number is user-definable. The setup default is In the ZDSMSCM subvolume, check the INITSTAT file for the recently configured TCP/IP port number. INITSTAT is created by DSM/SCM when INITENV is run. Configure OSS See the Open System Services Management and Operations Guide and the Open System Services Installation Guide for information about updating and maintaining OSS database files. See the Release Version Update Compendium for your J-series RVU and the IUG2 for new OSS features and for a summary of migration or installation issues. Install Specific OSS Files Using COPYOSS or PINSTALL For those products that are not managed by DSM/SCM, you must install them using COPYOSS or 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 the pinstall(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 archives in the ZOSSUTL subvolume. See the OSS Management and Operations Guide for a description of COPYOSS use or the copyoss(8) reference page in the OSS Shell and Utilities Reference Manual. Then use PINSTALL to install any pax archives in other subvolumes. See the OSS Management 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 changes impact where you install OSS packages onto your system. See Support Note S12018 for detailed information. See also the appropriate product s softdoc for any pre- or post-installation instructions. NOTE: To preserve the original inetd.conf file before using COPYOSS or PINSTALL the following steps must be done to prevent COPYOSS or PINSTALL from overwriting the original inetd.conf file: Save the original inetd.conf file by using the command: > mv inetd.conf smplinetd.conf After running COPYOSS or PINSTALL, if the original inetd.conf file needs to be restored, use the command: Run the inetd Process > mv smplinetd.conf inetd.conf Run 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 found on one of its sockets, inetd determines what service the socket corresponds to and invokes a program to service the request. Configure Specific Products (Post-System Load) 107

108 For those products that are not managed by DSM/SCM, you must install them using COPYOSS or PINSTALL. See the appropriate product s softdoc and installation instructions. Using OSS Unautomated Configuration and Startup Unautomated configuration and startup is described in Appendix B in the Open System Services Management and Operations Guide. Using OSS EasySetup (T0585) The OSS EasySetup product (T0585) is available for automated setup, as described in the Open System Services Installation Guide. OSS EasySetup is a series of TACL scripts that assist a site when configuring and installing a minimal OSS subsystem for the first time or when starting, stopping, or removing an OSS subsystem. 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 Storage Management Foundation User's Guide. Performance-critical applications that optimize the physical location of their data might need to specify the PHYSVOL option when creating data files, instead of relying on the SMF file-placement algorithm. NonStop SQL/MP must be up and running before you start SMF. CAUTION: (VDP): SWAP files TMF audit data DSM/SCM files To maintain data integrity, do not place these items on a virtual disk process 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 Facility The 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 master audit-trail disk process. The AUDITTRAILBUFFER parameter allows you to specify how many megabytes of buffer space to allocate for the audit-trail buffers. See the SCF Reference Manual for the Storage Subsystem for information on configuring the buffer size and check the DP2 softdoc for more information for J06.10 and later RVUs. See the Release Version Update Compendium for your J-series RVU for new feature information. Configure the WAN Manager If you have a SWAN or SWAN 2 concentrator: 108 Resuming Normal Operations

109 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. Set Up itp WebServer If itp WebServer was installed and was being used with the previous RVU, the same itp WebServer installation would not work after the RVU upgrade. To get the itp WebServer installation working (both T8996 and T8997) after an RVU upgrade, you must re-configure and set up itp WebServer at the same OSS location using the setup script. See the Release Version Update Compendium for your J-series RVU for new feature information. See the J06.15 Release Version Update Compendium for information about itp Secure WebServer 7.4. Re-deploy NonStop SOAP 4 If NonStop SOAP 4 was deployed and was being used with the previous RVU, the same SOAP 4 installation would not work after the RVU upgrade. To use NonStop SOAP 4 after an RVU upgrade, you must deploy the NonStop SOAP 4 version available with the new RVU in the existing NonStop SOAP 4 deployment directory, using the NonStop SOAP 4 deploy script. See the J06.15 Release Version Update Compendium for information about NonStop SOAP 4.1. Configure Specific Products (Post-System Load) 109

110 11 Backing Out the DSM/SCM Revision Products That Might Have Fallback Implications Review the J06.nn Release Version Update Compendium for this RVU and product softdocs to make sure that your installed products do not have migration and fallback implications. Open System Services Back up the OSS configuration database files before falling back. For more information, see the Open System Services Management and Operations Guide. Storage Management Foundation The record format of the system configuration database sometimes changes between RVUs and is automatically converted to the new format the first time the system is loaded. 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. 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 required SMF softdocs. Before Backing Out the Revision 1. Confirm that the Spooler is active and not 100 percent full. a. At a TACL prompt, start SPOOLCOM and issue a COLLECT, STATUS command. For example: 12> spoolcom $spls; collect, status COLLECT STATE FLAGS CPU PRI UNIT DATA FILE %FULL $S ACTIVE 3, $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 TMF 5> volume $dsmscm_vol.zdsmscm 6> RUN STARTSCM where $dsmscm_vol is the DSM/SCM volume. Start the Target Interface (ZPHITI) NOTE: With NonStop Software Essentials 4.0 and later, you can also use NonStop Software Essentials (instead of ZPHITI) to back out a software revision that has already been applied. For more information, see the NonStop Software Essentials User s Guide or online help. The section that follows describes only the ZPHITI method. 1. From the DSM/SCM subvolume, enter: 110 Backing Out the DSM/SCM Revision

111 RUN ZPHITI The TI Logon screen appears: 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 11NOV2004 (c) Hewlett Packard Development Company L.P., 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 :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 Request 1. 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 :18:03:03 Selection number: Submit a Backout Request 111

112 ============================================================================== Choose a target selection number from the list below. Status information is shown for requests still in progress. ============================================================================== 1 NEW CONFIG 2 DEFAULT ===========================More Targets PgDn/PgUp============================= F1-Select F15-Help F16-Return SF16-Exit Ready 2. In the Selection number field, enter the number corresponding to the logical target that you want to back out of (selection 2 in this example), and press F1. The Target Menu - Select Action screen appears: DSM Software Configuration Manager Target Menu - Select Action ============================================================================== \ELI Prior snapshot :18:03:03 DEFAULT Last S/W applied on SYS 00 on :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 :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 previous revision, 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 :18:03:03 DEFAULT Last S/W applied on SYS 00 on :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: 112 Backing Out the DSM/SCM Revision From: SYS 02 applied on :18:01 To: SYS 01 applied on :15:41

113 ============================================================================== F1-Submit request F15-Help F16-Return SF16-Exit Ready 4. Press F1 to submit the backout request. DSM/SCM automatically reapplies the previous software revision. While the backout request is processing, DSM/SCM displays the Backout - Processing Backout screen, which gives a description of the request, its processing status, and the location of the previous SYSnn software affected by the request. The screen is updated with current status information approximately every 15 seconds, as in these examples: DSM Software Configuration Manager Backout - Processing Backout ============================================================================== \ELI Prior snapshot :18:03:03 DEFAULT Last S/W applied on SYS00 on :18:01 Backout :10:59:34 ============================================================================== Request is being processed. Status information will appear below indicating progress. ============================================================================== Backout Awaiting start :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 :18:03:03 DEFAULT Last S/W applied on SYS00 on :18:01 Backout :11:00:39 ============================================================================== Request is being processed. Status information will appear below indicating progress. ============================================================================== Backout Processing :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 with operator instructions. A complete set of operator instructions might look like this: DSM Software Configuration Manager Backout - Complete Backout ============================================================================== \ELI Prior snapshot :18:03:03 DEFAULT Last S/W applied on SYS on :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. Submit a Backout Request 113

114 =============================================================================== 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. Update FIRMWARE. Run OSM to check firmware and perform firmware updates. T0287 HALTED STATE SVCS includes firmware changes. T0287 HALTED STATE SVCS includes firmware changes. 3. RUN ZDSMSCM.ZPHIRNM SYS00 4. Check for $0 EMS messages. Correct any errors indicated in the $0 EMS messages. Do not proceed until this step has been successfully completed. 5. Coldload is required. 6. Run merge_whatis if ZPHIRNM indicates it is needed. 7. Restart all applications. ============================================================================== 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 to modify these instructions before returning to the previous RVU. For instance, you might not need to change the firmware unless you have to replace hardware that can be supported only by the new RVU. 6. Press SF16 to exit the Target Interface. Monitor the Backout Process Using NonStop Software Essentials 1. 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: 114 Backing Out the DSM/SCM Revision

115 Monitor the Backout Process Using the Planner Interface 1. 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: Monitor the Backout Process Using the Planner Interface 115

116 12 Running ZPHIRNM to Reactivate the Previous Software Revision This step runs the ZPHIRNM program again to change the temporary names of the previous product files back to their actual names. Fallback Considerations for NonStop Software Essentials After ZPHIRNM If after migrating to this RVU, you decide to fall back to an RVU earlier than J06.13, you need to be aware of the fallback considerations for NonStop Software Essentials. NonStop Software Essentials 2.0 or later components are not compatible with NonStop Software Essentials 1.0 components. When you fall back, the ZPHIRNM step may rename the files in $SYSTEM.ZNSE, and you might not be able to continue using NonStop Software Essentials after reloading the system. These are the possible NonStop Software Essentials fallback scenarios you might encounter: If the T0894H02 or later server was already installed on the fallback RVU, there should be no problems. If the T0894H01 server was installed on the fallback RVU, you can revert to using the T0895V01 (Windows) or T0996V01 (Linux) client from another CMS, although this is not recommended. If possible, you should install the T0894H02 NonStop Software Essentials server SPR as described 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 either revert to using the DSM/SCM Planner Interface, or you can install the T0894H02 or later server manually as described in the Nonstop Software Essentials Installation and Quick Start Guide. Alerts Before running ZPHIRNM: Applications that use files that are being replaced should not be running. To avoid any possibility of conflict, stop all applications, except for the TMF subsystem, before running ZPHIRNM. You must have rename (purge) access to all files being renamed. You can ensure this access by running ZPHIRNM as the super ID (255,255). If you are connected to an Expand network, you might see a message stating that the NonStop SQL file, ZZSQLCI2, was not renamed during ZPHIRNM. However, on further examination of the log file, you may find that ZPHIRNM did finally rename the file, in which case you can ignore the error message and continue. Make sure that you drain the Spooler before running ZPHIRNM. If you drain the Spooler after running ZPHIRNM, an error message appears indicating that the spooler program and library versions 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 identify processes that currently have jobs open. Use the SPOOLCOM;JOB (STATE PRINT) command to determine which jobs are currently printing. 116 Running ZPHIRNM to Reactivate the Previous Software Revision

117 Take the appropriate action to ensure that these jobs either terminate when finished or are stopped. Drain the Spooler. To drain the Spooler, log on as a super group user (255,n), access SPOOLCOM, and enter the following command: Run ZPHIRNM SPOOLCOM> SPOOLER, DRAIN This command causes the Spooler to move from the active to the dormant state. CAUTION: Do not use the TACL STOP command to drain or stop the Spooler. Also, do not issue the TACL STOP command after you have issued the SPOOLCOM DRAIN command. The control file can be corrupted during the next warmstart or rebuild. For more information on draining the Spooler and recovery, see Chapter 1 in the Spooler Utilities Reference Manual. Using PREVIEW Mode You can do a preview run of ZPHIRNM to check that the target subvolumes (TSVs) and associated map files are consistent. Running ZPHIRNM in PREVIEW mode simulates the ZPHIRNM process without actually updating files or activating the configuration. In PREVIEW mode, ZPHIRNM indicates whether or not TMF needs to be up when running ZPHIRNM. Run ZPHIRNM 1. At a TACL prompt, enter from the DSM/SCM subvolume: > RUN ZPHIRNM $vol.sysnn where: $vol specifies the default current system load volume, usually $SYSTEM. SYSnn specifies the SYSnn subvolume named previously in the backout request. For example: > RUN ZPHIRNM $system.sys00 2. 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. Run ZPHIRNM 117

118 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 nonfatal error occurs, ZPHIRNM issues an error message and attempts to restore the subvolume it 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 message and 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 procedures and the DSM/SCM Messages Manual for a complete list of ZPHIRNM messages. 118 Running ZPHIRNM to Reactivate the Previous Software Revision

119 13 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations This chapter describes how to perform a system load of the previous RVU and how, as needed, to revert the CLIM software and/or firmware to the previous versions. NOTE: If your NonStop system does not have CLIMs installed, disregard the sections in this chapter that describe CLIM fallback procedures. Fallback Considerations for the Power Regulator Alerts The 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 the default Status High Performance Mode. Before 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 close the dialog box, a message dialog box appears to alert you that the system startup process 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 normal operation. If you must stop the system startup process, click Abort. (The abort process should take effect within 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 system to which you are falling back needs SPRs to support those components. See the CLuster I/O Module (CLIM) Software Compatibility Reference for this information. Check the list of fallback issues in the J06.nn Release Version Update Compendium, where J06.nn is the RVU to which you are falling back. Task Overview If 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 previous CLIM software is necessary or desirable, the CLIM must be reimaged, as described in these procedures. Refer to the CLuster I/O Module (CLIM) Software Compatibility Reference to determine whether reverting to the previous CLIM software is necessary for your fall back scenario. If your systems does not have CLIMs installed, you can disregard these steps. Fallback Considerations for the Power Regulator 119

120 Restoring the CLIMs assumes that you have saved the CLIM configurations by issuing the CLIMBKUP command before upgrading your system, as described in Back Up CLIM Configuration Files (page 46) and in the Cluster I/O Protocols (CIP) Configuration and Management Manual. Falling back to previous versions of CLIM software adds approximately one hour for each CLIM to the process of loading the system on the previous RVU. NOTE: When you fall back, you must restore CLIM configuration files saved from the same RVU as 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 RVU is: 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 used for the dedicated service LAN and for the Maintenance Providers, configuring the Storage CLIM for its role in the system, and configuring all the CLIMs with the system information you 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 restore more of the CLIM configurations by running a script that restores various aspects of the CLIM configuration 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 If Falling Back to J06.14 or an Earlier RVU Multiple Providers per CLIM functionality, which is first implemented with the J06.15 RVU, includes allowing a single CLIM to be associated with multiple data providers if the MULTIPROV attribute of the CLIM object is set to ON (enabled). NOTE: If you have the J06.08 through J06.14 RVU and are not planning to migrate to J06.15 or a later RVU, you can implement full Multiple Providers per CLIM functionality by acquiring the T0853H01^ACF SPR from Scout and installing it. If you need to fall back from J06.15 or a later J-series RVU to J06.14 or an earlier RVU that does not already have the T0853H01^ACF SPR installed, you must disable the MULTIPROV attribute to instruct CLIMs to follow pre-multiple Providers per CLIM behavior and use the sole provider specified by the PROVIDER attribute. For details, see the Cluster I/O Protocols (CIP) Configuration and Management Manual. (Optional) Prepare to Fall Back to Previous CLIM Firmware If you will be falling back to previous CLIM firmware using one of the down system methods, perform the appropriate action in the OSM Service Connection as described in Managing CLIM Firmware and Software (page 29). 120 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations

121 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-cycled during 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-n 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 system console or a CLIM DVD. If you do not have the correct software image on a system console, install it from the CLIM DVD for J-series by following the procedure in the CLuster IO Protocols (CIP) 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. This step uses the OSM Service Connection and either the CLIM Boot Service Configuration Wizard or the NonStop LAN DHCP DNS Configuration Wizard, depending on which wizard you have installed on your NonStop system console. a. Determine the IP address of the CLIM(s) you are going to downgrade. Use the OSM Service Connection to identify the Maintenance Interface IP Address for the CLIM. b. To determine if one ore more of the CLIMs you are downgrading is being used for DHCP, DNS, and BOOTP services, launch either the CLIM Boot Service Configuration Wizard or the NonStop Maintenance LAN DHCP DNS Configuration Wizard. Whichever wizard Before Halting the Processors 121

122 you have installed on your NonStop system console is launched from the Windows Start menu by selecting All Programs>HP OSM>, followed by the name of the wizard. NOTE: For detailed information about the appearance of and instructions for using the wizard you have installed on your NonStop system console, see the online help for that wizard. c. If the wizard confirms that any of the CLIMs you are downgrading are being used for DHCP, DNS, and BOOTP services, check the listed IP addresses to see if they correspond to the CLIMs you are downgrading. For information on how to use the wizard, see the online help for the wizard you are using. NOTE: If any CLIMs to be downgraded are being used for those services, you will use this information later, during the fallback step If Using CLIMs for BOOTP, DHCP, or DNS Services (page 123) 6. Obtain the system name, netmask, gateway, and IP address for the CLIMs. If this information is unavailable from your environmental documentation, continue with the next step to obtain it directly from your system. Otherwise, skip the next step. 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.N , DETAIL The NonStop host system name in this example is \BLJCQA2 and the maintenance interface IP address is b. Use the climcmd clim-name climconfig interface -info eth0 command from a TACL prompt for the CLIMs to obtain the netmask and gateway. For example: >climcmd N climconfig interface -info eth0 comforte SSH client version T9999J06_07Jul2008_comForte_SSH_0080 Interface : eth0 Interface Type : Physical Interface Jumbo Frame : NO IP Address : Netmask : In this example, the netmask is 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 OSSINFIL You must restore the SERVER #ZPLS entry in the OSS subsystem maintenance file OSSINFIL on all systems with OSS installed before halting the processors to fall back to J06.04 or earlier RVUs. If you commented out this entry when installing this RVU, use TEDIT to modify the entry as follows: TEDIT $SYSTEM.ZOSSINS.OSSINFIL Then change * SERVER #ZPLS to SERVER #ZPLS This change is required for correct startup of OSS. 122 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations

123 If Using CLIMs for BOOTP, DHCP, or DNS Services When falling back to the J06.04 RVU, if the CLIM or CLIMs you are downgrading are being used for BOOTP, DHCP, or DNS services instead of the system consoles on your LAN, you must migrate these services to the NonStop System Console. See the service procedure: Changing the DHCP, DNS, or BOOTP Server From CLIMs to System Consoles. Halt the Processors 1. 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. 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 Halted NOTE: If you are falling back on any NonStop system running J-series software except for the NonStop NS2000 series and the DHCP, DNS, and BOOTP services for your dedicated service LAN are hosted on CLIMs that you will reimage as part of this fall back, see Prepare the CLIMs (page 124) for instructions on copying the appropriate HSS files (this operation also copies DISKBOOT and ISP1040 files) for all applicable systems after you reimage the CLIM and before loading the system. NOTE: Firmware is backward compatible. HP recommends that you retain current firmware, and revert to previous firmware only when necessary. If necessary, revert the Server Blade firmware (HSS, DISKBOOT, and ISP1040), then hard reset all processor blades as follows: 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 Firmware If you are falling back to previous CLIM firmware using the down system method, use the CLIM Management Tool or the Down System CLIM Firmware Update Tool as described in Managing CLIM Firmware and Software (page 29). Reimage the CLIMs NOTE: Only reimage CLIMs if you need to revert their software to an older version. Check the CLuster I/O Module (CLIM) Software Compatibility Reference to determine which versions of the CLIM are compatible with the target RVU. Reimaging a CLIM must be performed by an HP authorized service provider. Service providers can refer to Reimaging or Downgrading a CLIM for information about reimaging CLIMs. Halt the Processors 123

124 For detailed instructions on reimaging a Gen8 CLIM using ilo 4, see Reimaging or Downgrading a CLIM. NOTE: If you have Gen8 CLIMs and need to fall back to a J-series RVU as far back as J06.08, you can continue to use the AC-powered Gen8 CLIMs as long as you install the required SPRs for the target RVU as described in the CLuster I/O Module (CLIM) Software Compatibility Reference. Prepare the CLIMs This procedure is necessary only if you reimaged a CLIM to revert CLIM software. 1. For each CLIM, set the IP address of eth0 through the ilo serial console. a. At the Linux prompt, log onto the CLIM. CLIMs are shipped with two default maintenance interface usernames and passwords: root/hpnonstop user/clim b. 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 CLIM dialog box, enter all the information that you gathered before starting this procedure. (In pre-abk versions of OSM Low-Level Link, the PCI Slot Configuration area shows the possible PCI slot configurations in multiple drop-down menus. (This area is disabled for Storage CLIMs.)) Sample Pre-ABK Version of OSM Low-Level Link, IP CLIM 124 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations

125 In ABK and later versions of OSM Low-Level Link, the PCI Slot Configuration area has the groups of possible IP CLIM configurations selectable from a single drop-down menu. Sample ABK and Later Versions of OSM Low-Level Link, IP CLIM The PCI Slot Configuration area is disabled for Storage CLIMs in pre-abk, ABK and post ABK versions of OSM Low-Level Link. Sample ABK or Later Versions of OSM Low-Level Link, Storage CLIM Be sure to select the CLIM type for the type of CLIM you are configuring from the Mode of operation pull-down menu. After entering the required information in the dialog box, press Prepare the CLIMs 125

126 Configure. Here is an example screen showing the CLIM preparation has successfully completed: Sample Pre-ABK Version of OSM Low-Level Link, IP CLIM Sample ABK or later Version of OSM Low-Level Link Version, IP CLIM 4. Click Yes. The CLIM reboots. 126 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations

127 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 that connect to the system disks: lunmgr approve yesall 6. For the two IP CLIMs configured with a Maintenance Provider (usually the first two IP CLIMs, for example, N /N for NonStop BladeSystems), configure the eth0:0 interface. Using the IP address and netmask of ZTCP0 and ZTCP1 you collected by using the SCF INFO CLIM DETAIL and CLIMCMD interface -info commands prior to starting the downgrade, and using the ilo serial console, enter these commands at the Linux prompt: climconfig interface -add eth0:0 climconfig ip -add eth0:0 -ipaddress netmask If you reimaged both CLIMs and they were being used to host DHCP, DNS, and BOOTP services on your dedicated service LAN, as determined in Prepare to Fall Back to Previous CLIM Software (page 121), and this is a J-series system that relies on these CLIMs to provide BOOTP servers (i.e., all NonStop systems running J-series software except for NS2000), you must log on to the OSM Low-Level Link and copy the system-specific HSS file to the CLIMs now before loading the system as described in Complete CLIM Setup (page 129). If this system does not need CLIM-based BOOTP services but other systems on your LAN do, you can perform this OSM Low-Level Link logon and copy HSS file procedure later. Load the System A normal system load consists of loading the operating system from disk into the memory of processor 0 or processor 1: 1. In the OSM Low-Level Link, select Start System. The System Load dialog box appears. 2. In the System Load dialog box, select $SYSTEM or a saved configuration. a. In the SYSnn field, enter nn, which is the number of the system subvolume that contains the version of the operating system you will load. 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. For a 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 might wait up to 30 seconds before the abort takes effect. CAUTION: Do not close the System Load dialog box while startup is in progress. If you attempt to close the dialog box, an OSM message box indicates that the system startup process will be stopped if you continue. If you stop a system startup before the operation finishes, the state of your system cannot be predicted. You might need to perform another system startup to enable the system to resume normal operation. If one or more of the startup event stream windows or startup TACL windows does not launch on the system console after a few minutes (5 to 8 minutes), abort system startup, close the Load the System 127

128 OSM Low-Level Link, reboot the system console, and restart the system load using the OSM Low-Level Link again. 6. Monitor the system startup process. Messages indicating the progress and completion of the system load, and the reload of processors indicated in the CIIN file, appear in these display locations on the system console. When the system load is complete (the operating system is loaded successfully into the memory of processor 0 or processor 1), the Detailed box on the System Load dialog box displays: SYSTEM STARTUP COMPLETE, NSK RUNNING ON PROCESSOR n If the system load fails, check for the appearance of any halt codes or messages. For recovery procedures, see the Processor Halt Codes Manual or Operator Messages Manual. After the operating system is running on the server, messages are no longer sent to the Details box. See the event messages sent to the startup event stream window. Complete the System Load (If Necessary) Loading the processors with the CIIN file is usually automatic. However, if the operating system loaded successfully into processor 0 or processor 1, but the commands in the CIIN file do not reload all remaining processors, use the following TACL RELOAD command. 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: 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 the system console screen: PROCESSOR RELOAD: nn Using the SSOCLIM * Option to Run SSOCLIM on All Available CLIMs For this RVU, SSOCLIM can be made to run on all available CLIMs by using the * option instead of 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 all available CLIMs when * is used. 128 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations

129 PASSWORD is the password to be used against a CLIM when CLIM NAME or IP is used or against all available CLIMs when * is used. FORCED, if specified, suppresses the warning instruction to run SSOCLIM on all the CLIMs. Complete CLIM Setup 1. Establish trust between the CLIM and the NonStop host system. If you are falling back to J06.09 (or to an RVU with T0682H02^ACC) or J06.10 (or to an RVU with T0682H02^ACI), you must run SSOCLIM as SUPER.SUPER. In all cases, you must run SSOCLIM twice, once with the root username and hpnonstop password, and once with the user username and clim password. a. At a TACL prompt, log on as SUPER.SUPER (for a fallback to J06.09 or J06.10) or as any SUPER group user. b. Enter SSOCLIM. The script prompts you for the CLIM name, IP address or DNS name of the CLIM. Enter that parameter. Then the script prompts you for the username and password. Use the root 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 upgrade procedures in Back Up CLIM Configuration Files (page 46). NOTE: The CLIM configuration files used during this procedure must be of the same RVU as the RVU to which you are falling back. For the J06.04 and J06.05 RVUs, rename and restore the backup files. For example, at the TACL prompt, enter: a. >FUP RENAME $DATA1.BCKJ0605.N , $DATA1.BCKJ0605.BACKUPGZ b. >CLIMRSTR N $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 N $SYSTEM.N 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 as failover pairs. For Storage CLIMS, you must know which pair of CLIMs are attached to a 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 return before rebooting the next CLIM. For Storage CLIMs, use SCF status disk $*. For IP and Telco CLIMs, use CLIMCMD psclim. >climcmd n psclim If you do not see any running processes, use the CLIM command to clear the log and start. For example (IP CLIM): >climcmd n clim clearlog; clim start For Storage CLIMs, after clearlog, you must reboot again. For example (Storage CLIM): Complete CLIM Setup 129

130 >climcmd s clim clearlog >climcmd s clim reboot-nodebug c. Reboot the other set of CLIMs, that is, the other CLIM in each failover pair or the other CLIM in each pair that connects to a particular disk. d. If the system disk is a SAS disk and you have SAS disk enclosures that contain the system disks (both primary and mirror), check the LUN manager status to be sure they are functional. 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 errors SCF> reset disk $* SCF> start disk $* - Say Yes when it prompts SCF> status disk $*-*, sel not started 4. If you reimaged a CLIM being used for DHCP, DNS, and BOOTP services on your LAN, use the OSM Low-Level Link from each system that relies on getting its HSS files as part of this BOOTP service (i.e., all NonStop systems running J-series software except for the NonStop NS2000 series) and use 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 current HSS version for each processor on the system 130 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations

131 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 after system discovery. Before system discovery, click Copy HSS Files on the toolbar or select Copy HSS Files from the Tools menu. After system discovery, select Copy HSS Files from the Tools menu. 6. If this is an IB CLIM, install third-party Informatica software for messaging and order sequencing. Complete CLIM Setup 131

132 NOTE: See Support Note SN (OSM application issues with Administrator user on NSC) for instructions on preventing authentication failures from occurring on NonStop System Consoles when using these OSM tools: Down System CLIM Firmware Update, Update HSS and Copy HSS file actions in OSM Low-Level Link, and connecting to a peer NSC from the NonStop Maintenance LAN DHCP DNS Configuration Wizard or the CLIM Boot Service Configuration Wizard. A fix of this problem is automatically installed when you run the Master Installer on NonStop System Console Installer DVD, Update 18 or later. Support Note S describes another workaround option if you do not have the Update 18 or later DVD. Revert Firmware (If Necessary) HP recommends running the latest firmware; however, if necessary, revert the following firmware to 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 documentation specific to your NonStop system for details.) c7000 enclosure firmware, if applicable to your system (Onboard Administrator firmware installed 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 or G16SE enclosure firmware (ME and ME FPGA), if applicable to your system S-series interoperability firmware, if applicable to your system (Service Processor and Service Processor 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 firmware while 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 COPYOSS or PINSTALL or both. For details, see Install Specific OSS Files Using COPYOSS or PINSTALL (page 107). NOTE: Features introduced in J06.12 affect the default security settings for OSS. See Support Note S12018 for detailed information. Verify That the System Is Started Verify 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. 132 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations

133 A Using DSM/SCM With NonStop Software Essentials to Install SPRs NOTE: Before performing the steps in this appendix install NonStop Software Essentials by using the procedures in the NonStop Software Essentials Installation and Quick Start Guide. SPRs provide new features between RVUs or correct software problems from a previous RVU. This appendix describes tools available for investigating SPRs and instructions on how to install SPRs. CAUTION: Do not apply any SPR to an RVU without first verifying (by using Scout for NonStop Servers, for example) that the SPR can be installed on that specific J-series RVU. See the J06.nn Release Version Update Compendium for this RVU and the Interactive Upgrade Guide 2 (IUG2) for information on SPRs that you might need to apply to your current RVU before upgrading to this RVU and connecting to a G-series or H-series system. Tools for Managing SPRs Always keep an SPR log file that lists which SPRs have been reviewed, selected, and installed on your 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 Servers DSM/SCM Using Scout for NonStop Servers, you can display detailed information about RVUs, SPRs, and prerequisites for SPRs. You can also access: Outage Prevention Notifications (OPNs) Hotstuff messages Support Notes RVU (softdocs) and softdoc addendums After researching available SPRs, you can download those you consider appropriate for your system directly to your workstation and then use FTP to transfer downloaded SPRs to your server, or you can request tape delivery. DSM/SCM has automatic features that can help you keep records of SPRs. You can use the NonStop Software 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 SPR You can also use the DSM/SCM Archive to export SPRs to different volumes. See the NonStop Software Essentials User s Guide for more information. Tools for Managing SPRs 133

134 SPRNOTES You can use SPRNOTES to research an SPR before installing it. Read the installation instructions and considerations documented in the SPRNOTE, which includes: A summary of SPR contents Lists of SPRs required for this SPR Installation considerations, including tasks to perform before and after running DSM/SCM A summary of problems corrected A summary of known problems remaining Keep a copy of each SPRNOTE and record the status of the related SPR. For example, record whether the SPR is not applicable, is already installed, or needs to be installed. Install SPRs Using DSM/SCM With NonStop Software Essentials The steps for using DSM/SCM to install SPRs are the same as those for installing a SUT. Save the Current Configuration First, save the current system configuration database CONFIG file. Use the SCF SAVE command: 1. At a TACL prompt, start SCF: 2> SCF 2. List the saved configuration files. 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 through This example saves the current system configuration to the file $SYSTEM.ZSYSCONF.CONF1101: -> SAVE CONFIGURATION 11.1 The 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 you specify that you do not want to replace the existing file, SCF does not overwrite the file. You must enter another SAVE command to save the current configuration file. Determine the Current SYSnn There 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 must use a different SYSnn subvolume to create a new software revision if NonStop Software Essentials indicates 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:18 COPYRIGHT 2003 Hewlett-Packard Development Company, L.P. System name \ELI EXPAND node number 033 Current SYSnn SYS Using DSM/SCM With NonStop Software Essentials to Install SPRs

135 System number Software release ID J Issue a TACL FILEINFO command on $system.*.osimage to list the SYSnn subvolumes on your system and determine which one is open. $SYSTEM.SYS00 CODE EOF LAST MODIFIED OWNER RWEP PExt SExt OSIMAGE DEC2007 9:57 255,255 NUNU $SYSTEM.SYS01 CODE EOF LAST MODIFIED OWNER RWEP PExt SExt OSIMAGE APR2008 8:56 255,255 NUNU At a TACL prompt, enter a STATUS 0,0 command to see which SYSnn subvolume is currently being used: 3> status 0,0 System \ELI Process Pri PFR %WT Userid Program file Hometerm 0,0 201 P R ,255 $SYSTEM.SYS01.NMONTOR $YMIOP.#CLCI Swap File Name: $SYSTEM.#0 Receive the SPR Into the DSM/SCM Archive Before Starting DSM/SCM Start TMF if it is not already running: > TMFCOM START TMF Bring the SPR Into the DSM/SCM Archive 1. 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 Manage NonStop Software link on the NonStop server Tools & Links tab. 3. Click Receive software under the Software Installation group on the NonStop Software Essentials home 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 SPR After the SPR has been received into the Archive, you can copy it. To create a new software configuration that includes the SPR: Install SPRs Using DSM/SCM With NonStop Software Essentials 135

136 1. From the Configuration Revisions page, select the configuration you are updating and click Create in the New Revision group. The new software revision page appears. 2. Select SPRs to be added to the current configuration and click Copy to. Build the New Revision After you have created a new software revision, prepare to install it on your target systems by building it into an executable form: 1. On the New software revision page, click Build/Apply to load the Build/Apply options page. 2. 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 that the Spooler is active and not 100 percent full before executing the Build/Apply request. At a TACL prompt, start SPOOLCOM and issue a COLLECT, STATUS command. 5. Select Scheduling, Output, SYSGEN, TSV Location, and File Placement tabs and configure as appropriate for your system. See the NonStop Software or online help (Building and Applying a New Configuration topic) for more information about these Build/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 operator instructions. Run ZPHIRNM During the Build/Apply phase, DSM/SCM places product files in their subvolumes with temporary (fabricated) file names so that the new files do not conflict with the file names of currently running programs. After the Build/Apply finishes, run the ZPHIRNM program on the target system to: Rename the files that currently have actual file names with fabricated names. These files become obsolete when the new files are renamed. 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: 136 Using DSM/SCM With NonStop Software Essentials to Install SPRs

137 > 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/SCM Messages Manual for a complete list of ZPHIRNM messages. If Running INSTALL^TEMPLATES Is Required If the operator instructions state that you should run INSTALL^TEMPLATES to update EMS template files, 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, the INSTALL^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 by INSTALL^TEMPLATES. When you follow the suggested procedure, a nonresident template file is not 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 to provide required information. For information on the INSTALL^TEMPLATES arguments, print the usage notes: -> volume $system.zinsaids -> load /keep 1/ TACLMACS -> install^templates /out outdev/ help where outdev is the name of the desired output device. 3. Choose a location on $SYSTEM to keep updated template files: If Running INSTALL^TEMPLATES Is Required 137

138 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 the new system is loaded, the old template files named in the last execution of INSTALL^TEMPLATES are opened instead of the new files. To use the new RTMPLATE and TEMPLATE EMS files created 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 next SYSGEN and system load. The following error message might occur when running the INSTALL^TEMPLATES macro: >$SYSTEM.SYSTEM.SCF /NAME $Z019,INV :INBUF.1,OUTV :OUTBUF.1/ Current Nonresident template file is: $SYSTEM.TEMPLATE.NEWNRES TEMPLATE and NONRESIDENT files must be different: $SYSTEM.TEMPLATE.NEWNRES *** INSTALL^TEMPLATES: Terminated due to error *** The error message indicates that the template and nonresident files specified in the INSTALL^TEMPLATES command are identical to those on the current subvolume. The INSTALL^TEMPLATES macro tries to create the newres and newnres files, but stops when it finds that these template files already exist. To correct the problem: 1. Rename the current files: tacl> rename newres, oldres tacl> 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 \TINY Copyright Tandem Computers Incorporated 1981, 1983, SECURE ($SYSTEM.TEMPLATE.NEWRES,$SYSTEM.TEMPLATE.NEWNRES),"NUNU" *** INSTALL^TEMPLATES: Completed sucessfully *** If a System Load Is Required If OSM is installed and configured, use these instructions to load your RVU. Halt the Processors 1. If necessary, log on to the OSM Low-Level Link. 2. On the toolbar, select Processor Status to open the Processor Status dialog box. 138 Using DSM/SCM With NonStop Software Essentials to Install SPRs

139 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 Load A normal system load consists of loading the operating system from disk into the memory of processor 0 or processor 1. See Chapter 9: Loading This RVU, for information on performing a system load. Start Your Applications and Processes After you have reloaded the processors and the Processor Status screen shows all processors executing the NonStop operating system, you can start your applications and processes. See Chapter 10: Resuming Normal Operations. Verify that your system is up and running. See Chapter 9: Loading This RVU. If a System Load Is Required 139

140 B Using DSM/SCM With the Planner Interface to Install SPRs SPRs provide new features between RVUs or correct software problems from a previous RVU. This appendix describes tools available for investigating SPRs and instructions on how to install SPRs. CAUTION: Do not apply any SPR to an RVU without first verifying (by using Scout for NonStop Servers, for example) that the SPR can be installed on that specific J-series RVU. See the J06.nn Release Version Update Compendium for this RVU and the Interactive Upgrade Guide 2 (IUG2) for information on SPRs that you might need to apply to your current RVU before upgrading to this RVU and connecting to a G-series or H-series system. Tools for Managing SPRs Always keep an SPR log file that lists which SPRs have been reviewed, selected, and installed on your 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 Servers DSM/SCM SPRNOTES Using Scout for NonStop Servers, you can display detailed information about RVUs, SPRs, and prerequisites for SPRs. You can also access: Outage Prevention Notifications (OPNs) Hotstuff messages Support Notes RVU (softdocs) and softdoc addendums After researching available SPRs, you can download those you consider appropriate for your system directly to your workstation and then use FTP to transfer downloaded SPRs to your server, or you can request tape delivery. DSM/SCM has automatic features that can help you keep records of SPRs. You can use the DSM/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 SPR You can also use the DSM/SCM Archive to export SPRs to different SYSnns. See the DSM/SCM User s Guide for more information. You can use SPRNOTES to research an SPR before installing it. Read the installation instructions and considerations documented in the SPRNOTE, which includes: A summary of SPR contents Lists of SPRs required for this SPR Installation considerations, including tasks to perform before and after running DSM/SCM 140 Using DSM/SCM With the Planner Interface to Install SPRs

141 A summary of problems corrected A summary of known problems remaining Keep a copy of each SPRNOTE and record the status of the related SPR. For example, record whether the SPR is not applicable, is already installed, or needs to be installed. Install SPRs Using DSM/SCM With the Planner Interface The steps for using DSM/SCM to install SPRs are the same as those for installing a SUT. Save the Current Configuration First, save the current system configuration database CONFIG file. 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 This example saves the current system configuration to the file $SYSTEM.ZSYSCONF.CONF1101: -> SAVE CONFIGURATION 11.1 The 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 you specify that you do not want to replace the existing file, SCF does not overwrite the file. You must enter another SAVE command to save the current configuration file. Determine the Current SYSnn There 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 must use 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:18 COPYRIGHT 2003 Hewlett-Packard Development Company, L.P. System name \ELI EXPAND node number 033 Current SYSnn SYS01 System number Software release ID J Issue a TACL FILEINFO command on $system.*.osimage to list the SYSnn subvolumes on your system and determine which one is open. $SYSTEM.SYS00 CODE EOF LAST MODIFIED OWNER RWEP PExt SExt OSIMAGE DEC2007 9:57 255,255 NUNU Install SPRs Using DSM/SCM With the Planner Interface 141

142 $SYSTEM.SYS01 CODE EOF LAST MODIFIED OWNER RWEP PExt SExt OSIMAGE APR2008 8:56 255,255 NUNU At a TACL prompt, enter a STATUS 0,0 command to see which SYSnn subvolume is currently being used: 3> status 0,0 System \ELI Process Pri PFR %WT Userid Program file Hometerm 0,0 201 P R ,255 $SYSTEM.SYS01.NMONTOR $YMIOP.#CLCI Swap File Name: $SYSTEM.#0 Receive the SPR Into the DSM/SCM Archive Before Starting DSM/SCM Start TMF if it is not already running: > TMFCOM START TMF Bring the SPR Into the DSM/SCM Archive 1. 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 the software input a name based on information received from the SPR input. You can enter a new name if you want. 4. In the Receive Software Request dialog box, click Input source to display the Request Source Options dialog box. 5. If the SPR has been received on disk or has been restored from tape to disk, click Volume.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 SPR After the SPR has been received into the Archive, you can copy it. To create a new software configuration 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 configuration and click Copy to. 142 Using DSM/SCM With the Planner Interface to Install SPRs

143 Build the New Revision After you have created a new software revision, prepare to install it on your target systems by building it into an executable form: 1. In the New software revision dialog box, click Build/Apply to list options for your Build/Apply. The Build/Apply Request dialog box appears with all selections dimmed and unavailable. In a few minutes, the dialog box is refreshed with defaults selected. 2. 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 dialog box informs you that SYSGEN is required, check that the Spooler is active and not 100 percent full before executing the Build/Apply request. At a TACL prompt, start SPOOLCOM and issue a COLLECT, STATUS command. 5. Select Scheduling, Output, SYSGEN, TSV Location, and File Placement options and configure as appropriate for your system. See the DSM/SCM User s Guide or online help (Building and Applying a New Configuration topic) for more information about these Build/Apply Request options. 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 operator instructions. Print Operator Instructions From the Target Interface (ZPHITI) 143

144 Run ZPHIRNM During the Build/Apply phase, DSM/SCM places product files in their subvolumes with temporary (fabricated) file names so that the new files do not conflict with the file names of currently running programs. After the Build/Apply finishes, run the ZPHIRNM program on the target system to: Rename the files that currently have actual file names with fabricated names. These files become obsolete when the new files are renamed. 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/SCM Messages Manual for a complete list of ZPHIRNM messages. If Running INSTALL^TEMPLATES Is Required If the operator instructions state that you should run INSTALL^TEMPLATES to update EMS template files, 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, the INSTALL^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 by INSTALL^TEMPLATES. When you follow the suggested procedure, a nonresident template file is not 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 144 Using DSM/SCM With the Planner Interface to Install SPRs

145 NOTE: If you run the INSTALL^TEMPLATES macro with no arguments, you are prompted to provide required information. For information on the INSTALL^TEMPLATES arguments, print the usage notes: -> volume $system.zinsaids -> load /keep 1/ TACLMACS -> install^templates /out outdev/ help where outdev is the name of the desired output device. 3. Choose a location on $SYSTEM to keep updated template files: tacl>volume $system.template 4. 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 the new system is loaded, the old template files named in the last execution of INSTALL^TEMPLATES are opened instead of the new files. To use the new RTMPLATE and TEMPLATE EMS files created 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 next SYSGEN and system load. The following error message might occur when running the INSTALL^TEMPLATES macro: >$SYSTEM.SYSTEM.SCF /NAME $Z019,INV :INBUF.1,OUTV :OUTBUF.1/ Current Nonresident template file is: $SYSTEM.TEMPLATE.NEWNRES TEMPLATE and NONRESIDENT files must be different: $SYSTEM.TEMPLATE.NEWNRES *** INSTALL^TEMPLATES: Terminated due to error *** The message indicates that the template and nonresident files specified in the INSTALL^TEMPLATES command are identical to those on the current subvolume. The INSTALL^TEMPLATES macro tries to create the newres and newnres files, but stops when it finds that these template files already exist. To correct the problem: 1. Rename the current files: tacl> rename newres, oldres tacl> 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 \TINY Copyright Tandem Computers Incorporated 1981, 1983, If Running INSTALL^TEMPLATES Is Required 145

146 SECURE ($SYSTEM.TEMPLATE.NEWRES,$SYSTEM.TEMPLATE.NEWNRES),"NUNU" *** INSTALL^TEMPLATES: Completed sucessfully *** If a System Load Is Required If OSM is installed and configured, use these instructions to load your RVU. Halt the Processors 1. If necessary, log on to the OSM Low-Level Link. 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 Load A normal system load consists of loading the operating system from disk into the memory of processor 0 or processor 1. See Chapter 9: Loading This RVU, for information on performing a system load. Start Your Applications and Processes After you have reloaded the processors and the Processor Status screen shows all processors executing the NonStop operating system, you can start your applications and processes. See Chapter 10: Resuming Normal Operations. Verify that your system is up and running. See Chapter 9: Loading This RVU. 146 Using DSM/SCM With the Planner Interface to Install SPRs

147 C Copying the DSM/SCM, NonStop Software Essentials, and SWID SPRs from the SUT Using NonStop Software Essentials To better ensure that the SUT installation proceeds smoothly, copy the DSM/SCM, NonStop Software Essentials server, and SWID SPRs located on the SUT to your system and perform the other tasks described in Copying the DSM/SCM, NonStop Software Essentials, and SWID SPRs from the SUT Using NonStop Software Essentials (page 147) before you receive and install the RVU SUT. In the upgrade checklist table in Upgrade Checklist (page 42), the step that describes and links to the procedures described in this appendix is located at the start of the table. NOTE: In order for the procedure described in Copy (RESTORE) the DSM/SCM Server, NonStop Software Essentials Server, and SWID Product Versions from the SUT to Disk (page 150) to display the NonStop Software Essentials client screens needed to perform it, you must already have a functioning and interoperating set of NonStop Software Essentials server and client products installed on your system. You must copy the SWID SPR when you copy the DSM/SCM SPR from the SUT to your system. (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.) After you copy the DSM/SCM, NonStop Software Essentials server, and SWID SPRs from the SUT as described in Copy (RESTORE) the DSM/SCM Server, NonStop Software Essentials Server, and SWID Product Versions from the SUT to Disk (page 150), install the latest version of the NonStop Software Essentials client product as described in Install the Latest Version of the NonStop Software Essentials Client (page 155). If your system uses the DSM/SCM Planner Interface instead of NonStop Software Essentials, see Copying the DSM/SCM and SWID SPRs from the SUT Using the Planner Interface (page 156). Alerts If you install the NonStop system console DVD Update 23 on a given system s console and install the NonStop Software Essentials 4.0 client before the Receive has been performed to completion, this Warning message is displayed when you connect the open NonStop Software Essentials 4.0 client to older NonStop Software Essentials service objects (servers). Alerts 147

148 The NonStop Software Essentials 4.0 client will in fact work with an older version of the NonStop Software Essentials server, but the NonStop Software Essentials 4.0 functionality will not be available on that system. To achieve that functionality, you must install the NonStop Software Essentials 4.0 server (T0894H02^AAF) as well as its client. To install the NonStop Software Essentials 4.0 server version (T0894H02^AAF), you can either migrate your system to J06.19 or install this version of the server by SPR. or an earlier J-series RVU, the NonStop Software Essentials server SPR (T0894H02) will not be present on the SUT. Instead, you must use Scout to install the latest T0894H02 SPR to your host system as described in If Migrating to J06.12 or an Earlier RVU, Install the Latest NonStop Software Essentials Server SPR Using Scout (page 153). For instructions on identifying the product versions of the NonStop Software Essentials, DSM/SCM, and SWID SPRs currently installed on the host system and on the SUT, see Determine the Product Version of NonStop Software Essentials Server on the Host System and the SUT (page 149), Determine the Product Version of DSM/SCM on the Host System and the SUT, and Determine the SWID Product Version on the Host System and the SUT (page 149), and Install the Latest Version of the NonStop Software Essentials Client (page 155). Save the current configuration database. (See Save the Current Configuration File (CONFxxyy) (page 47)). 148 Copying the DSM/SCM, NonStop Software Essentials, and SWID SPRs from the SUT Using NonStop Software Essentials

149 Keep the startup TACL windows, the EMS Event Stream window, and the NonStop Software Essentials client interface windows open whenever you are performing a Build/Apply. Otherwise, Build/Apply errors will result. If you receive an error indication in the Request Status window, you might have to re-initiate the Build/Apply. See the DSM/SCM Messages Manual to learn the nature and severity of the problem. Determine the Product Version of NonStop Software Essentials Server on the Host System and the SUT CAUTION: The NonStop Software Essentials server product (T0894H02) has been on the SUT since J If you are preparing to install a SUT for J06.12 or an earlier J-series RVU, you will not find the NonStop Software Essentials SPR on the SUT. Instead, you must use Scout to install the latest orderable NonStop Software Essentials server SPR on your system when you copy the DSM/SCM and SWID SPRs from the SUT. For more information, see If Migrating to J06.12 or an Earlier RVU, Install the Latest NonStop Software Essentials Server SPR Using Scout (page 153). To determine which product version of NonStop Software Essentials server (T0894H02) is currently installed on your system, use the VPROC command. At a TACL prompt, enter: > VPROC $SYSTEM.ZNSE.HTTPSRVR If the NonStop Software Essentials server product version on the SUT does not match the version on your system, copy the SUT version to your system as described in Copy (RESTORE) the DSM/SCM Server, NonStop Software Essentials Server, and SWID Product Versions from the SUT to Disk (page 150). For information about installing the NonStop Software Essentials client product, see Install the Latest Version of the NonStop Software Essentials Client (page 155). Determine the Product Version of DSM/SCM on the Host System and the SUT To determine which product version of DSM/SCM is currently installed on your system, use the VPROC command to determine 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 For comparison, the DSM/SCM version on the SUT is T6031H02^ADB. If the DSM/SCM server product version on the SUT does not match the version on your system, copy the SUT version to your system as described in Copy (RESTORE) the DSM/SCM Server, NonStop Software Essentials Server, and SWID Product Versions from the SUT to Disk (page 150). Determine the SWID Product Version on the Host System and the SUT Using the VPROC command, identify the SWID SPR on the system. For comparison, the SWID version on the SUT is T9298H02^AAV. If the SWID product version on the SUT does not match the version on your system, copy the SUT version to your system as described in Copy (RESTORE) the DSM/SCM Server, NonStop Software Essentials Server, and SWID Product Versions from the SUT to Disk (page 150). Alerts 149

150 nl nl nl nl Copy (RESTORE) the DSM/SCM Server, NonStop Software Essentials Server, and SWID Product Versions from the SUT to Disk CAUTION: The NonStop Software Essentials server product SPR (T0894H02) has been on the SUT since J If you are preparing to install the SUT for J06.12 or an earlier J-series RVU, you will not find the NonStop Software Essentials SPR on the SUT during the Copy (RESTORE) the DSM/SCM Server, NonStop Software Essentials Server, and SWID Product Versions from the SUT to Disk (page 150) procedure. Instead, you must use Scout to install the latest orderable NonStop Software Essentials server SPR on your system you copy the DSM/SCM and SWID SPRs from the SUT as described in If Migrating to J06.12 or an Earlier RVU, Install the Latest NonStop Software Essentials Server SPR Using Scout (page 153). To copy the H02 product version of DSM/SCM, NonStop Software Essentials server, and the SWID product from this RVU to disk, at a TACL prompt, enter the RESTORE command: >RESTORE/OUT $S.#nn.DSM/$tape, ($S.#nn.DSM/$tape, ($*.?6031*.*, *.?9298*.*,?0894*.*), VOL $DSMSCM, LISTALL where nnn is the RVU number (J06) and where $tape is the name of the tape drive containing this RVU. The Windows (T0895) and Linux (T0996) versions of the NonStop Software Essentials clients are independent products and must be installed as SPRs from Scout as described in Install the Latest Version of the NonStop Software Essentials Client (page 155). Receive the H02 DSM/SCM, NonStop Software Essentials Server, and SWID SPRs 1. Start TMF and DSM/SCM if they are not already running: 2. > TMFCOM START TMF > VOLUME $dsmscm_vol.zdsmscm > RUN STARTSCM 3. 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, NonStop Software Essentials server, 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.E0894H02 $DSMSCM.E9298H02 Your Receive Software Input Source tab should look similar to this: 150 Copying the DSM/SCM, NonStop Software Essentials, and SWID SPRs from the SUT Using NonStop Software Essentials

151 9. Click Submit to run the request immediately. (The request takes less than 5 minutes to finish.) The Request Status page is loaded into the work panel. Create a New Software Revision for H02 DSM/SCM, NonStop Software Essentials, and SWID SPRs 1. From the New Revision page, select the target system being upgraded and the current revision of the system being upgraded. Select Create. The New Revision page is loaded with the last software revision that was built for the 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, T0894, and T9298 are copied from the Archive to the new software revision. Create a New Software Revision for H02 DSM/SCM, NonStop Software Essentials, and SWID SPRs 151

152 3. From the New software revision table, verify that the new version of DSM/SCM, NonStop Software Essentials server, and SWID are included in the new software revision. 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/14: DSM/SCM, NonStop Essentials server, and SWID c. Click OK to save your changes to the revision notes Build and Apply the DSM/SCM H02 Software Product Revision The Build process creates an activation package of products contained in the new software revision. During the Apply process, the activation package is transferred to the target system. When the Apply request is finished, a snapshot is automatically created and returned to the host. Because you are building and applying only a few files, it should take less than an hour before the Build and Apply requests are finished and the snapshot is returned. When the Build and Apply requests are 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. NonStop Software Essentials runs the Build/Apply requests and displays a Status page that 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 been received into the host database, wait until the status shows that all activities are complete. Run the INSTALL^TEMPLATES Macro EMS templates are used by EMS to format EMS messages. After running ZPHIRNM, and if notified to do so by DSM/SCM, run the INSTALL^TEMPLATES TACL macro to install DSM/SCM EMS templates in their proper locations. NOTE: The files newres and newnres are used as temporary names until the next SYSGEN and system load. The INSTALL^TEMPLATES macro is located in the $SYSTEM.ZINSAIDS subvolume and invokes the TEMPLI 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 troubleshooting information, see If Running INSTALL^TEMPLATES Is Required (page 137). 152 Copying the DSM/SCM, NonStop Software Essentials, and SWID SPRs from the SUT Using NonStop Software Essentials

153 If Migrating to J06.12 or an Earlier RVU, Install the Latest NonStop Software Essentials Server SPR Using Scout The NonStop Software Essentials server SPR is not present on the RVU SUTs J06.12 or earlier. If you are migrating to J06.12 or an earlier J-series RVU, you must install the latest T0894H02 SPR from Scout to your system disk. Restart Applications You can now start your application software. Follow your site s procedures for executing the system configuration and startup (command) files to accomplish this. DSM/SCM is often started automatically by a system command file. If not, you must start DSM/SCM manually as described in Start DSM/SCM (page 153). Before Starting DSM/SCM 1. Check that TMF is started: > TMFCOM STATUS TMF 2. Verify your current configuration against the cold start configuration in PATHHOST (or PATHTARG) to check that the current configuration reflects all changes you have made. 3. If necessary, run the PATHCOLD macro from the ZDSMSCM subvolume to cold start the Pathway configuration. Start DSM/SCM 1. 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 \ NOTICE: * If the hometerm chosen during INITENV, $zhome, * is not currently in a paused state, STARTSCM and DSM/SCM * server processes may hang indefinitely. Be sure this * hometerm has been paused! Because the $ZHOME reliable home-term process is not an interactive process and is always paused, no action is necessary. 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 If Migrating to J06.12 or an Earlier RVU, Install the Latest NonStop Software Essentials Server SPR Using Scout 153

154 $Z03N: TCP TCP-T, STARTED 2. If necessary, press Enter to have STARTSCM run the IPM6031 TACL macro automatically. This step takes several minutes. STARTSCM: A new version of DSM/SCM has been installed and IPM6031 needs to be run. You can either exit and run IPM6031 manually or continue and IPM6031 will be run for you. Enter <CR> to continue or BREAK to exit. Verify that the SUT Version of DSM/SCM is Installed To verify that the SUT version of DSM/SCM is now 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 VPROC command should now display the DSM/SCM SPR version T6031H02^ADB. Verify that the SUT or Scout Version of the NonStop Software Essentials Server is Installed To verify that the latest version of NonStop Software Essentials server SPR is now installed on your system, either copied from the SUT or installed from Scout, enter at the TACL prompt: > VPROC T0894 > VPROC $SYSTEM.ZNSE.HTTPSRVR The VPROC command should now display the NonStop Software Essentials server version T0894H02 and its 3-character product version update ID. Verify that the SUT Version of SWID Is Installed To verify that the SUT version of SWID is now installed on your system, enter at the TACL prompt: > \DRP08.$SYSTEM.SYSTEM 101> vproc swid The VRPROC command should now display the SWID version T9298H02^AAV. Recovery for Problems While Installing the H02 Version of DSM/SCM If you encounter problems while installing the H02 version of DSM/SCM, see the DSM/SCM User s Guide. If NonStop Errors Are Displayed See the DSM/SCM EMS Messages manual for information regarding the error message and the DSM/SCM User s Guide for information on deleting a Build/Apply request. Cancel Pending Build/Apply Requests NOTE: If you inadvertently close the Status page, reopen it by clicking on the Request Name link on the Request List page. Click the Cancel button. The cancel request action takes a few minutes to finish. 154 Copying the DSM/SCM, NonStop Software Essentials, and SWID SPRs from the SUT Using NonStop Software Essentials

155 NOTE: If you cannot cancel the Build request through NonStop Software Essentials, use the DSM/SCM Target Interface (ZPHITI) to cancel the request. See the NonStop Software Essentials User s Guide and online help for more information. NOTE: If you inadvertently close the Status dialog box, reopen it by selecting Requests> Requests list and then double-clicking the request. Install the Latest Version of the NonStop Software Essentials Client After you have successfully copied the latest versions of DSM/SCM, NonStop Software Essentials server, and SWID SPRs from the SUT to the system, install the latest version of the NonStop Software Essentials client. The NonStop Software Essentials client product that you install on a Windows console (T0895) or Linux CMS (T0996) is not provided on the SUT. Instead, use Scout to install the appropriate client s SPR or use the client installer that is provided on the HP Insight Control for NonStop DVD for the RVU, which ships with the HP NonStop System Console Installer DVD, Update 17 or later. For detailed pre-installation requirements and installation information for the Windows and Linux versions of the NonStop Software Essentials client, see the NonStop Software Essentials Installation and Quick Start Guide. The NonStop Software Essentials client SPR for Windows is T0895V02^AAB. The NonStop Software Essentials client SPR for Linux is T0996V02^AAC. Install the Latest Version of the NonStop Software Essentials Client 155

156 D Copying the DSM/SCM and SWID SPRs from the SUT Using the Planner Interface NOTE: You must have installed both the DSM/SCM SPR and the corresponding client version before you receive an RVU SUT. All newly shipped NonStop systems will have the latest DSM/SCM SPR installed. The latest DSM/SCM client version is available only on the SUT unless you have ordered new system consoles. Always install the latest SWID PVU at the same time you install a new DSM/SCM PVU to avoid a fingerprint or mismatched 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.) Your newly 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 2012 or Windows 2008 (64-bit) system console, use the instructions for installing SWID and DSM/SCM using NonStop Software Essentials in Using DSM/SCM With NonStop Software Essentials to Install SPRs (page 133). Alerts To determine Determine the Product Version of DSM/SCM on the Host System and the SUT and. Save the current configuration database. (See Save the Current Configuration File (CONFxxyy) (page 47)). 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/Apply errors will result. If you receive an error indication in the Request Status window, you might have to re-initiate the Build/Apply. See the DSM/SCM Messages Manual to learn the nature and severity of the problem. Determine the Product Version of DSM/SCM on the Host System and SUT To determine which product version of DSM/SCM is currently installed on your system, use the VPROC command to determine 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 If your VPROC commands do not display the version for this RVU, install the correct DSM/SCM product version by following the procedures in Copy (RESTORE) the DSM/SCM Server, NonStop Software Essentials Server, and SWID Product Versions from the SUT to Disk (page 150). For comparison, the DSM/SCM version on the SUT is T6031H02^ADB. Determine the SWID Product Version on the Host System and SUT Using the VPROC command, identify the SWID SPR. For comparison, the SWID version on the SUT is T9298H02^AAV. Determine the Product Version of DSM/SCM on the Client To determine which product version of DSM/SCM client software is installed, start the DSM/SCM Planner Interface. Before prompting you to log on, the About DSM/SCM window briefly displays version information. For example: 156 Copying the DSM/SCM and SWID SPRs from the SUT Using the Planner Interface

157 You can also bring up the above dialog box with Help/About; this method keeps the window open until you close it. To install the DSM/SCM client, see Install the DSM/SCM Client Software (page 165). Copy (RESTORE) the H02 DSM/SCM Product Version to Disk (If Necessary) To copy the H02 product version of DSM/SCM and the SWID product from this RVU to disk, at a TACL prompt, enter the RESTORE command: >RESTORE/OUT $S.#nnn.DSM/$tape, ($*.E6031H02.*, *.E9298H02.*), VOL $DSMSCM, LISTALL where nnn is the RVU number (J06) and where $tape is the name of the tape drive containing this RVU. Receive the H02 SWID and DSM/SCM SPRs 1. Start TMF and DSM/SCM if they are not already running: 2. > TMFCOM START TMF > VOLUME $dsmscm_vol.zdsmscm > RUN STARTSCM 3. 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) 157

158 9. Click OK. You are returned to the Receive Software Request dialog box. 10. Click OK to run the request immediately. (The request takes less than 5 minutes to finish.) The Status dialog box appears. Wait until the display for the Request activity summary appears as Complete, and then close the Status window. For example: 158 Copying the DSM/SCM and SWID SPRs from the SUT Using the Planner Interface

159 11. Select Window>Refresh to update the Software in Archive dialog box to include the received software. Create a New Software Revision for H02 DSM/SCM and SWID SPRs 1. In the Configuration Revisions dialog box, select the target system being upgraded and the current revision of the system being upgraded. Select New software revision. DSM/SCM opens the New dialog box listing the products in the last software revision that was built for the target. Allow several minutes for the dialog box to appear. 2. In the Software in Archive dialog box, select the DSM/SCM software you just received and click 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 and SWID 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 Revision The Build process creates an activation package of products contained in the new software revision. During the Apply process, the activation package is transferred to the target system. When the Apply request is finished, a snapshot is automatically created and returned to the host. Because you are building and applying only a few files, it should take less than an hour before the Build Create a New Software Revision for H02 DSM/SCM and SWID SPRs 159

160 and Apply requests are finished and the snapshot is returned. When the Build and Apply requests are finished, the new software is placed in the current SYSnn subvolume. 1. In the New software revision dialog box, click Build/Apply to display the options for your Build/Apply. It might take several minutes for DSM/SCM to assemble the build information. During this time, the Build/Apply Request dialog box appears with all selections dimmed and unavailable. In a few minutes, the dialog box is refreshed with defaults selected. The name assigned to the Build/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 is automatically 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 been received 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 configuration revision containing the H02 DSM/SCM SPR. 160 Copying the DSM/SCM and SWID SPRs from the SUT Using the Planner Interface

161 Rename the Applied DSM/SCM H02 Files By Running ZPHIRNM 1. Stop DSM/SCM: > VOLUME $dsmscm_vol.zdsmscm > RUN STOPSCM where $dsmscm_vol is the DSM/SCM volume. 2. Run ZPHIRNM: > RUN ZPHIRNM $volume.sysnn where SYSnn is the current SYSnn (because no SYSGEN or system load is required). 3. 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 88). Run the INSTALL^TEMPLATES Macro EMS templates are used by EMS to format EMS messages. After running ZPHIRNM, and if notified to do so by DSM/SCM, run the INSTALL^TEMPLATES TACL macro to install DSM/SCM EMS templates in their proper locations. NOTE: The files newres and newnres are used as temporary names until the next SYSGEN and system load. The INSTALL^TEMPLATES macro is located in the $SYSTEM.ZINSAIDS subvolume and invokes the TEMPLI 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 troubleshooting information, see If Running INSTALL^TEMPLATES Is Required (page 137). Restart Applications You can now start your application software. Follow your site s procedures for executing the system configuration and startup (command) files to accomplish this. DSM/SCM is often started automatically by a system command file. If not, you must start DSM/SCM manually as described in Start DSM/SCM (page 161). Before Starting DSM/SCM 1. Check that TMF is started: > TMFCOM STATUS TMF 2. Verify your current configuration against the cold start configuration in PATHHOST (or PATHTARG) to check that the current configuration reflects all changes you have made. 3. If necessary, run the PATHCOLD macro from the ZDSMSCM subvolume to cold start the Pathway configuration. Start DSM/SCM 1. Run the STARTSCM macro from the ZDSMSCM subvolume to start DSM/SCM: Rename the Applied DSM/SCM H02 Files By Running ZPHIRNM 161

162 > RUN STARTSCM These messages appear: 8> startscm DSM/SCM Process Startup Function - STARTSCM - T6031H02 - (31MAR2003) Copyright Hewlett Packard Development Company L.P \ NOTICE: * If the hometerm chosen during INITENV, $zhome, * is not currently in a paused state, STARTSCM and DSM/SCM * server processes may hang indefinitely. Be sure this * hometerm has been paused! Because the $ZHOME reliable home-term process is not an interactive process and is always paused, no action is necessary. 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. This step takes several minutes. STARTSCM: A new version of DSM/SCM has been installed and IPM6031 needs to be run. You can either exit and run IPM6031 manually or continue and IPM6031 will be run for you. Enter <CR> to continue or BREAK to exit. Verify That the Correct SPR for DSM/SCM is Installed To 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 For comparison, the DSM/SCM SPR for this RVU is is T6031H02^ADB. Verify That SWID Is Installed Using the VPROC command, identify the SWID SPR. For comparison, the SWID version on the SUT is T9298H02^AAV. Recovery for Problems While Installing the H02 Version of DSM/SCM If you encounter problems while installing the H02 version of DSM/SCM, see the DSM/SCM User s Guide. 162 Copying the DSM/SCM and SWID SPRs from the SUT Using the Planner Interface

163 If NonStop Errors Are Displayed See the DSM/SCM EMS Messages manual for information regarding the error message and the DSM/SCM User s Guide for information on deleting a Build/Apply request. Cancel Pending Build/Apply Requests 1. 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, use the DSM/SCM Target Interface (ZPHITI) to cancel the request. See the DSM/SCM User s Guide 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 ZDSMSCM NOTE: This installation procedure is restricted to those who use the Planner Interface with DSM/SCM instead of NonStop Software Essentials. It is also restricted to customers who are using a 32-bit NonStop system console running Windows Server Do not perform this procedure if you are using a 64-bit console. NOTE: Before you begin, back up your current DSM/SCM folder to save the configuration information and the Planner Interface version. Check that unnecessary PC programs are not running before you begin the DSM/SCM client installation and that no DSM/SCM Build or Applies are in progress. If you have Planner Interface installed on your system and need to fall back to an earlier RVU, you can use the newly installed client software. NOTE: HP recommends that both the DSM/SCM product version (T6031H02) and DSM/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 Version To determine which version of DSM/SCM client software is installed, start the DSM/SCM Planner Interface. Before prompting you to log on, the About DSM/SCM window briefly displays version information. See Determine the Product Version of DSM/SCM on the Host System and the SUT (page 149). Determine the Current IP Address and Port Number When you install DSM/SCM client software, you are prompted to enter the IP address of the host system with which DSM/SCM communicates and the IP port number for the DSM/SCM Winsock service. 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 163

164 6. Make a note of the IP address and port number. 7. Close the dsmscm.ini file. Copy the ZDSMSCM Client File From the Host NOTE: Both the Planner Interface and ZDSM.exe are supported on 32-bit NonStop system consoles only. ZDSM.exe is not supported on 64-bit Nonstop system consoles, which include those running Windows Server 2008 or Windows Server If you use it on a 64-bit console, this error message is displayed. 1. From the Windows Start menu, select Run and enter the command CMD. An example response is: Microsoft Windows XP [Version ] (C) copyright 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 DSMSCM 5. Enter: ftp <ip-address>, where ip-address is the IP address of your NonStop server. For example, ftp An example response is: Connected to osmlanx FTP SERVER T9552H02 (Version H02 TANDEM 03MAY2006) ready User ( : (none)): super.super 331 Password required for SUPER.SUPER. 6. Enter the super.super password. An example response is: 164 Copying the DSM/SCM and SWID SPRs from the SUT Using the Planner Interface

165 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: 200 PORT command successful. 150 Opening data connection for zdsmexe ( ,3212d) (2334 bytes). 226 Binary Transfer complete. ftp: bytes received in 0.20 seconds Kbytes/sec. ftp> 11. Move zdsm.exe file into the desired folder on the NonStop console, such as c:\dsmscm or C:\DSMJ06nn. 12. Double click on zdsm.exe to expand the files into the desired folder. Install the DSM/SCM Client Software 1. Using Windows Explorer, double-click Setup.exe. A DSM/SCM Setup screen appears, and an Enter Object Manager Server Class dialog box appears with the default OM 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. NOTE: Private software product groups can be used only by the planner who creates the grouping. Shared software product groups can be used by other planners. For more information on these options, see the DSM/SCM User s Guide. (NonStop Software Essentials only supports shared product groups and HP recommends using shared product groups for PI as well.) Install the DSM/SCM Client From ZDSMSCM 165

166 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, based on your Windows operating system: 6. Click Next to accept the default. You are now prompted to enter an IP address: 7. Enter the IP address for the host system with which DSM/SCM communicates (see Determine the Current IP Address and Port Number (page 163)), and click Next. NOTE: If DSM/SCM is not currently configured to communicate with a host system, accept the default IP address. You can always change this value later by editing the dsmscm.ini file. You are now prompted to enter an IP port number for the Winsock service that is within a specific range: 8. Enter the IP port number for the Winsock service (see Determine the Current IP Address and Port Number (page 163)), and click Next. NOTE: If DSM/SCM is not currently configured to communicate with a host system, accept the default IP port number. You can always change this value later by editing the dsmscm.ini file. You are now prompted to enter the host system name. 9. Enter the host system name (or \noname if DSM/SCM is not currently configured to communicate with a host system), and click Next to continue. You are asked if you would like to run DSM/SCM. Click NO when you are asked if you would like to run DSM/SCM. 10. Click No. The setup program adds the DSM/SCM client software to the Windows Start>Programs menu. You can start the DSM/SCM Planner Interface or CNFGINFO tool from the Start>Programs>DSM_SCM submenu. For example: 166 Copying the DSM/SCM and SWID SPRs from the SUT Using the Planner Interface

167 E Updating SWAN Concentrator CLIP Firmware If necessary, you can update the SWAN or SWAN 2 concentrator CLIP firmware after you have completed a system load of the new RVU. See either the SWAN Concentrator Installation and Support Guide or the SWAN 2 Concentrator Installation and Support Guide. 167

168 Acronyms This list provides the full names of acronyms used in this guide. BOOTP Boot protocol. CCSA Common Communications ServerNet adapter. CIIN Command interpreter input. CIP Cluster I/O Protocols. CLCI Cold load command interpreter. CLIM CLuster I/O Module. CLIP Communications line interface processor. CNSL Console. ConMgr Concentrator manager process CRU Customer replaceable unit. DHCP Dynamic Host Configuration Protocol. DLL Dynamic link library. 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. 168 Acronyms

169 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. 169

170 Index Symbols $SYSTEM.ZTCPIP, 105 $SYSTEM.ZTCPIP subvolume, 86 $ZCDB, 20 $ZPLS, Common Communication ServerNet Adapter (CCSA), 27 A AUDITTRAILBUFFER parameter, DP2 and RDF performance, 108 B Back up files backing up important files before upgrading, 46 ZTCPIP subvolume, 86 Build process, DSM/SCM, 64, 77 Build/Apply request, defined, 19 C CBEXE product determining version on host system, 149, 156 verifying version, 154, 162 CIIN file, 98, 127 disabled, 98, 127 CLCI sessions, 100 CLIM compatibility with host RVUs, 31, 33 fallback procedure, 119 firmware, 29, 98 installing CLIM software, 21 CLIM Management Tool, 29 CNSL session, 100 Commands RELOAD, 101, 128 STATUS TAPE, 53 CONFIG file saving, 47, 134, 141 use in loading the previous RVU, 127 use in loading the system, 98 D Determine if HSS firmware needs to be upgraded, 95 Determine if system firmware needs to be upgraded, 94 DSM/SCM build process, 64, 77 prepackaged reports, 133, 140 Target Interface, 21 E EasySetup, 58, 70 F Fabricated file names, 20 Fallback summary of major tasks, 21 ZPHIRNM, 116 Fibre Channel ServerNet Adapter (FCSA), 26 G Gigabit 4-port ServerNet Adapter (G4SA), 27 I inetd process, 107 INITSTAT, 107 INSTALL^TEMPLATES instructions, 137, 144 using with DSM/SCM, 152, 161 Installing the DSM/SCM client from ZDSMSCM, 163 Interoperability audit format issues, 54 SPRs for NonStop BladeSystems and NonStop Systems, 55 itp WebServer considerations, 109 K Kernel-managed swap files, 53 L Loading the J-series RVU, 91 Loading the system, 98, 127, 139, 146 M merge_whatis, 104 Migration issues, 31 MR-Win6530 terminal emulator startup windows on, 100 N New software revision, DSM/SCM, 74 New software revision, NonStop Software Essentials, 61 NonStop Cluster switch firmware, 28 NonStop SOAP 4 considerations, 109 NonStop Software Essentials, changing profile information, 62 NonStop System Console Installer DVD, 15 NonStop TCP/IP configuration files, 105 NonStop TCP/IPv6 files, 87 NSKCOM, 53 O OSS EasySetup, 108 Root Name Server $ZPNS, 61, 74 P Pcleanup utility, 104 Planner Interface, changing profile information, 75 PORTCONF file, 106 Post-installation configuring OSS, Index

171 configuring RDF, 108 configuring SMF, 108 updating TCP/IP configuration files, 105 PREVIEW mode, 89 Processor type in CONFTEXT file, 20 Profiles, target, changing information, 62, 75 PROTOCOL file configuration file location, 106 R RDF, 108 RELOAD command, 101, 128 Remote Database Facility, 108 S SCF testing the tape subsystem, 52 verifying critical processes, 50 verifying disks, 52 Scout for NonStop Servers, 14 ServerNet adapter firmware, 25 SERVICES file, 107 SMF, interoperability and configuration, 108 SOAP 4 see NonStop SOAP 4 Software revision, 19 Spooler backing up, command for, 88 checking status of collector, 53 COLLECT, STATUS command, 65, 79, 110, 136, 143 DRAIN command, 88 draining, 46 SPRNOTES, 134, 140 SPRs interoperability, 54 Status dialog box, reopening, 85, 155 SUT, maximum size of, 14 SWAN and SWAN 2 concentrator firmware, 28 Swap file space, checking, 53 SYSnn subvolumes listing, 47 System configuration file, 134, 141 Z ZcccGP files, 86 ZCNFDEFS, 86 ZINSAIDS subvolume, 152, 161 ZMODGP, 20 ZMODGP, in Preview mode, 88 ZPHIRNM PREVIEW mode, 89 reactivating previous software revision, 116 running, 86, 136, 144 ZPHITI canceling a Build/Apply request, 85, 163 starting, 110 T TACL RELOAD command, 21, 101 TAEXE, 149, 154, 156, 162 Target subvolumes (TSVs), 20 Target systems, changing profile information, 62, 75 TEMPLI program, 152, 161 Token Ring ServerNet Adapter (TRSA), 28 TRM2000, 14 U Update the HSS firmware, 96 Update the system firmware, 96 V VPROC command, 149,