J06.15 Software Installation and Upgrade Guide

(1)

J06.15 Software Installation and Upgrade

Guide

HP Part Number: 710337-003 Published: May 2015 Edition: J06.15 RVU

(2)

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.

The information contained herein is subject to change without notice. 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)

1 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...21

2 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

J06.04...31

Compiling C++ Programs to Run on RVUs Earlier Than J06.04...31

SQL/MX Versioning Feature Removed...31

CLIM...31

J06.05...32

AF_UNIX Release 2 Migration and Fallback...32

Migrating to AF_UNIX Release 2...32

Falling Back to An Earlier Version of AF_UNIX...33

CLuster I/O Module (CLIM) Software Compatibility...33

J06.06...34

CLuster I/O Module (CLIM) Software Compatibility...34

DSM/SCM Upgrade Issues/Interoperability SPR Requirements...34

J06.07...34

Falling Back to iLO Firmware T0848AAA...34

DSM/SCM Upgrade Issues/Interoperability SPR Requirements...35

J06.08...35

NonStop SQL/MX...35

J06.09...35

SQL/MX 2.3.4 Requires JDBC T2 Driver...35

BladeCluster Solution Multi-Zone Support...35

J06.10...35

NonStop SOAP 4...35

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 3.6...36

iTP WebServer 7.2...36

Expand Enhancements...36

J06.11...36

Changes to SSOCLIM Privilege Requirement...37

J06.12...37

HP SUM...37

Considerations for Fallback to J06.11...37

J06.13...37

Safeguard...37

Considerations for Fallback to J06.11...37

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

J06.14...38

Halt and Hard Reset Processors When Upgrading to J06.14...38

HP Power Regulator...38

Safeguard...39

SQL/MX Release 3.2...39

J06.15...39

CLIM Fallback Considerations for Multiple Providers per CLIM...39 4 Contents

(5)

Gen8 CLIMs...39

Halt and Hard Reset Processors When Upgrading to J06.15...39

NonStop Server for Java 7.0...39

NonStop SOAP 4.1...39

NonStop Software Essentials 2.1.0...40

Safeguard...40

SQL/MX Release 3.2.1...40

4 Upgrade Checklist...41

Required Information Checklists...41

Upgrade Checklist...42

5 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...57

6 Installing a SUT for This RVU Using NonStop Software Essentials...58

Alerts for Installing a SUT...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...69

7 Installing a SUT for This RVU Using the Planner Interface...70

Alerts for Installing a SUT...70

Receive New Software Into the Archive...70

Create a New Software Revision...74

Build and Apply the New Software Revision...77

Recovery for Problems Installing This RVU SUT or SPRs...85 Contents 5

(6)

8 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...90

9 Loading This RVU...91

Alerts...93

Perform Updates...93

1. 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...95

2. Halt the Processors...96

3. (Conditional): Update the System Firmware...96

4. (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...97

5. (Required Only for Upgrade from J06.13 or Earlier to J06.14 or Later) Perform a Hard Reset...97

6. Upgrade the CLIM Software...98

7. (Optional) Update the CLIM Firmware...98

8. Loading the System...98

Steps for Loading the System...98

Completing the System Load (If Necessary)...101

Verifying That the System Is Started...101

Updating Firmware (If Necessary)...102

After the System Load...102

10 Resuming Normal Operations...103

Revive the Down Half of the Mirrored Disk...103

Your Core License...103

Start System Applications...103

Before Starting DSM/SCM...103

Initialize SQL for NonStop SQL/MP...103

Cold Start the Pathway Configuration...104

Start DSM/SCM...104

Run merge_whatis...104

Configure Specific Products (Post-System Load)...105

Update NonStop TCP/IP Configuration Files...105

Step 1: Copy the Sample TCP/IP Files Into $SYSTEM.ZTCPIP (Optional)...105

Step 2: Check the PROTOCOL File (Optional)...106

Step 3: Optional: For Planner Interface, Ensure That PORTCONF and SERVICES Files Are Complete...106

Configure OSS...107

Install Specific OSS Files Using COPYOSS or PINSTALL...107 6 Contents

(7)

Run the inetd Process...107

Using OSS Unautomated Configuration and Startup...108

Using OSS EasySetup (T0585)...108

Configure SMF (Optional)...108

Configure the Remote Database Facility...108

Configure the WAN Manager...108

Set Up iTP WebServer...109

Re-deploy NonStop SOAP 4...109

11 Backing Out the DSM/SCM Revision...110

Products That Might Have Fallback Implications...110

Open System Services...110

Storage Management Foundation ...110

Before Backing Out the Revision...110

Start the Target Interface (ZPHITI)...110

Submit a Backout Request...111

Monitor the Backout Process Using NonStop Software Essentials...114

Monitor the Backout Process Using the Planner Interface...115

12 Running ZPHIRNM to Reactivate the Previous Software Revision...116

Fallback Considerations for NonStop Software Essentials After ZPHIRNM...116

Alerts...116

Drain the Spooler (Optional)...116

Run ZPHIRNM...117

Using PREVIEW Mode...117

Run ZPHIRNM...117

13 Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal

Operations ...119

Fallback Considerations for the Power Regulator...119

Alerts...119

Task Overview...119

Before Halting the Processors...120

If Falling Back to J06.14 or an Earlier RVU...120

(Optional) Prepare to Fall Back to Previous CLIM Firmware...120

Prepare to Fall Back to Previous CLIM Software...121

When Falling Back to the J06.04 or Earlier RVU...122

Modify OSSINFIL...122

If Using CLIMs for BOOTP, DHCP, or DNS Services...123

Halt the Processors...123

While the Processors Are Halted...123

(Optional) Fall Back to Previous CLIM Firmware...123

Reimage the CLIMs...123

Prepare the CLIMs...124

Load the System...127

Complete the System Load (If Necessary)...128

Using the SSOCLIM * Option to Run SSOCLIM on All Available CLIMs...128

Complete CLIM Setup...129

Revert Firmware (If Necessary)...132

Install Specific OSS Files (If Necessary)...132

Verify That the System Is Started...132

A Using DSM/SCM With NonStop Software Essentials to Install SPRs...133

Tools for Managing SPRs...133

Scout for NonStop Servers...133

DSM/SCM...133

SPRNOTES...134 Contents 7

(8)

Install SPRs Using DSM/SCM With NonStop Software Essentials...134

Save the Current Configuration...134

Determine the Current SYSnn...134

Receive the SPR Into the DSM/SCM Archive...135

Bring the SPR Into the DSM/SCM Archive...135

Create a New Software Configuration That Includes the SPR...135

Build the New Revision...136

Run ZPHIRNM...136

If Running INSTALL^TEMPLATES Is Required...137

If a System Load Is Required...138

Halt the Processors ...138

Perform a System Load...139

Start Your Applications and Processes...139

B Using DSM/SCM With the Planner Interface to Install SPRs...140

Tools for Managing SPRs...140

Scout for NonStop Servers...140

DSM/SCM...140

SPRNOTES...140

Install SPRs Using DSM/SCM With the Planner Interface...141

Save the Current Configuration...141

Determine the Current SYSnn...141

Receive the SPR Into the DSM/SCM Archive...142

Bring the SPR Into the DSM/SCM Archive...142

Create a New Software Configuration That Includes the SPR...142

Build the New Revision...143

Run ZPHIRNM...144

If Running INSTALL^TEMPLATES Is Required...144

If a System Load Is Required...146

Halt the Processors ...146

Perform a System Load...146

Start Your Applications and Processes...146

C Copying the DSM/SCM, NonStop Software Essentials, and SWID SPRs from

the SUT Using NonStop Software Essentials...147

Alerts...147

Determine the Product Version of NonStop Software Essentials Server on the Host System and the SUT...149

Determine the Product Version of DSM/SCM on the Host System and the SUT...149

Determine the SWID Product Version on the Host System and the SUT...149

Copy (RESTORE) the DSM/SCM Server, NonStop Software Essentials Server, and SWID Product Versions from the SUT to Disk...150

Receive the H02 DSM/SCM, NonStop Software Essentials Server, and SWID SPRs ...150

Create a New Software Revision for H02 DSM/SCM, NonStop Software Essentials, and SWID SPRs ...151

Build and Apply the DSM/SCM H02 Software Product Revision...152

Run the INSTALL^TEMPLATES Macro...152

If Migrating to J06.12 or an Earlier RVU, Install the Latest NonStop Software Essentials Server SPR Using Scout...153

Restart Applications...153

Start DSM/SCM...153 8 Contents

(9)

Verify that the SUT Version of DSM/SCM is Installed...154

Verify that the SUT or Scout Version of the NonStop Software Essentials Server is Installed...154

Verify that the SUT Version of SWID Is Installed...154

Recovery for Problems While Installing the H02 Version of DSM/SCM ...154

If NonStop Errors Are Displayed...154

Install the Latest Version of the NonStop Software Essentials Client...155

D Copying the DSM/SCM and SWID SPRs from the SUT Using the Planner

Interface...156

Alerts...156

Determine the Product Version of DSM/SCM on the Host System and SUT...156

Determine the SWID Product Version on the Host System and SUT...156

Determine the Product Version of DSM/SCM on the Client...156

Copy (RESTORE) the H02 DSM/SCM Product Version to Disk (If Necessary)...157

Receive the H02 SWID and DSM/SCM SPRs ...157

Create a New Software Revision for H02 DSM/SCM and SWID SPRs ...159

Build and Apply the DSM/SCM H02 Software Product Revision...159

Rename the Applied DSM/SCM H02 Files By Running ZPHIRNM...161

Run the INSTALL^TEMPLATES Macro...161

Restart Applications...161

Start DSM/SCM...161

Verify That the Correct SPR for DSM/SCM is Installed...162

Verify That SWID Is Installed...162

Recovery for Problems While Installing the H02 Version of DSM/SCM ...162

If NonStop Errors Are Displayed...163

Install the DSM/SCM Client From ZDSMSCM ...163

Determine Your DSM/SCM Client Software Version...163

Determine the Current IP Address and Port Number...163

Copy the ZDSMSCM Client File From the Host...164

Install the DSM/SCM Client Software...165

E Updating SWAN Concentrator CLIP Firmware...167

Acronyms...168

Index...170

(10)

Tables

1 Tasks and Tools for Backing Out to the Previous SYSnn ...21

2 Maintenance Entity (ME) Firmware File Names and Locations...23

3 Maintenance Entity (ME) FPGA File Names and Locations...24

4 Server Blade Firmware for All NonStop System Running J-Series Software Except for the NS2000 Series System...25

5 Blade Element Firmware for NonStop NS2000 Series Systems...25

6 ServerNet Adapters Used With J-Series NonStop Systems...25

7 J-Series ServerNet Adapters Firmware Information...28

8 Updateable Firmware for the NonStop ServerNet 6770 and 6780 Cluster Switch File Names and Locations...29

9 Updateable Firmware for S-series Interoperability...30

10 NonStop SQL/MX and Supported RDF Versions...35

11 Required Information Checklist, Before You Start ...41

12 Information to Gather During the Upgrade (Checklist) ...42

13 Upgrade Checklist...42

14 Interoperability SPRs for G-Series RVU Systems Connected Through Expand to H-Series or J-Series RVU Systems...55

15 Interoperability SPRs for H-Series RVU Systems Connected through ServerNet to J-Series RVU Systems ...55

16 Interoperability SPRs for G-Series RVU Systems Connected through ServerNet to J-Series RVU Systems...55

17 Interoperability SPRs for G-Series RVU Systems Connected through ServerNet to H-Series RVU Systems...55

18 SPRs for Software Migration and Software Management Operations Between G-Series, H-Series and J-Series RVU-Based Systems...56

19 System Load Paths in Order of Use for FCDM-Load...91

(11)

About This Document

This guide describes:

• Upgrading the initial J06.15 RVUthrough the use ofSUTrefreshes, if necessary.

• Falling back to a previous SYSnn.

Supported RVUs

This manual supports the J06.15.00 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,OSMclient 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 configuringOSS.

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

(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.hheader 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: 123.00

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) athttp://www.hp.com/go/nonstop-docs.

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

(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

Publication Date Product Version Part Number February 2013 N.A. 710337–001

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 todocsfeedback@hp.com.

Include the document title, part number, and any comment, error found, or suggestion for improvement you have concerning this document.

(14)

1 Overview of Installing This RVU

For information on installingSPRs, 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-seriesSUTis 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 hasCLIMs 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.

• TheIUG2simplifies 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,SPRanalysis, 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:

https://onepoint.nonstop.compaq.com/buildpage.asp.

(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 www.hp.com/go/hpsim. For more information on installing and getting started with NonStop

(16)

Software Essentials server and client components, see the NonStop Software Essentials Installation

and Quick Start Guide.

T-Number Software Product

T0894 NonStop Software Essentials Server

T0895 NonStop Software Essentials Client (Windows)

T0996 NonStop Software Essentials Client (Linux)

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.

nl

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-basedOSM SPRreleased 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

(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 J06.12. 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.

(18)

DSM/SCM and This RVU

CAUTION: Before you install the SUT, you mustcopy 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 manageOSSfiles. 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 forDLLs.

• Creating aSIT is not supported in J-series RVUs.

OSBUILD SPR

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:

Target NonStop System RVU SPR H06.10 and H06.11 T0431H01ÂAK H06.09 T0431H01ÂAH H06.08 T0431H01ÂAN H06.07 T0431H01ÂAM H06.05 and H06.06 T0431H01ÂAL

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/SCMmanages and controls the distribution, installation, and activation of publicDLLs 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 theManage OSS Filesoption 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

(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:www.hp.com/go/hpsim.

T-Number Software Product

T0894 NonStop Software Essentials Server

T0895 NonStop Software Essentials Client (Windows)

T0996 NonStop Software Essentials Client (Linux)

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

(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 theirTSVs 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 SYSnnbeing activated and if:

◦

The configuration being activated contains a ZCNFDEFSTSV

◦

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_PROCESSOR_TYPE System NSE-M NB50000c, NB50000c-cg, NB54000c, NB54000c-cg, NS2200 series, NS2100, and NS2000 series

Check the CONFTEXT file to ensure that the following entries are present. They are needed for the implicit DLLs: SYSTEM_IMPLICIT_INIT_FILES TANDEMÎMPLICITÎNIT^FILES; SYSTEM_IMPLICIT_CORE_FILES TANDEMÎMPLICIT^CORE^FILES; SYSTEM_IMPLICIT_FS_FILES TANDEMÎMPLICIT^FS^FILES; SYSTEM_IMPLICIT_MCP_FILES TANDEMÎMPLICIT^MCP^FILES; SYSTEM_IMPLICIT_ETC_FILES TANDEMÎMPLICITÊTC^FILES;

This example shows a CONFTEXT file:

$TEMP CONFIGXX 2> type conftext ALLPROCESSORS: SYSTEM_PROCESSOR_TYPE NSE-M; SYSTEM_VOLUME_SUBVOL $SYSTEM.SYS00; SYSTEM_LIBRARY_CODE_FILES TANDEM^LIBRARY^CODE^FILES; SYSTEM_PROCESS_CODE_FILES TANDEM^PROCESS^CODE^FILES; SYSTEM_PROCESS_LIBRARY_FILES TANDEM^PROCESS^LIBRARY^FILES;

(21)

STANDARD_MICROCODE TANDEM^STANDARD^MICROCODE; MICROCODE_FILES TANDEM^MICROCODE^FILES; FILES_TO_COPY_TO_NEW_SYSTEM TANDEM^FILES^TO^COPY; SYSTEM_IMPLICIT_INIT_FILES TANDEMÎMPLICITÎNIT^FILES; SYSTEM_IMPLICIT_CORE_FILES TANDEMÎMPLICIT^CORE^FILES; SYSTEM_IMPLICIT_FS_FILES TANDEMÎMPLICIT^FS^FILES; SYSTEM_IMPLICIT_MCP_FILES TANDEMÎMPLICIT^MCP^FILES; SYSTEM_IMPLICIT_ETC_FILES TANDEMÎMPLICITÊTC^FILES; FORMATTER_TEMPLATE_FILES TANDEM^FORMATTER^TEMPLATE^FILES; INITIAL_COMINT_INFILE $DSMSCM.SYS.CIIN;

Installing CLIM Software

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

Documented in This Chapter... Use This Tool...

To Perform This Task...

“Backing Out the DSM/SCM Revision ” (page 21)

DSM/SCM Target Interface (ZPHITI) 1. Submit a backout request.

Chapter 12: “Running ZPHIRNM to Reactivate the Previous Software Revision”

DSM/SCM ZPHIRNM program 2. Reactivate the previous software

revision.

“Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations ” (page 119)

OSM Low-Level Link 3. Load the HP NonStop operating

system and, if CLIMs are installed, load the CLIM software from the previous revision into the first processor.

“Falling Back on the CLIMs, Loading the Previous RVU, and Resuming Normal Operations ” (page 119)

TACL RELOAD command 4. Reload the remaining processors.

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

(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 atwww.hp.com/go/nonstop-docs.

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 isMEfirmware and MEFPGAfirmware on the ServerNet switches located in c7000 enclosures, onVIOlogic boards, and (optionally) inIOAMs.

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.

(23)

Table 2 Maintenance Entity (ME) Firmware File Names and Locations Default Location File Name Component Firmware Name SYSnnsubvolume M2805

ServerNet Switch (IOAM enclosure)

ME firmware (see Caution below)

SYSnn subvolume M4805

ServerNet Switch (c7000 enclosure)

Blade ME firmware (see Caution below)

SYSnnsubvolume M1805

VIO enclosure logic board ME firmware for IME in

G16SE and VIO enclosures (see Caution below)

For more information on managing ME firmware, see:

• The planning guide or hardware installation manual for your system.

• The online help in the OSM Low-Level Link or 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 isMEfirmware on the ServerNet Switch Board object in eachIOAMof 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: SelectSystem>Group >IOAM Enclosure> IOAM> ServerNet Switch Board.

2. Right-click the ServerNet Switch Board object and selectActions.

3. In the Actions dialog box, selectME Firmware Updateand 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: SelectSystem>Enclosure 100

>ServerNet Switch. The switches are labeled 100.2.5 and 100.3.7. You can select either switch.

2. Right-click the ServerNet Switch object and selectActions.

5. Repeat for the other ServerNet Switch.

6. If the system includes an (optional) enclosure 101, repeat the process for both switches in that enclosure. (The switches in Enclosure 101 are labeled 101.2.5 and 101.3.7.)

Updating ME Firmware on a VIO Enclosure and G16SE Enclosure

There is ME firmware on the VIO Logic Board object in each VIO enclosure.

(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 selectActions.

5. Repeat for theVIO 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 www.hp.com/go/nonstop-docs.

Table 3 Maintenance Entity (ME) FPGA File Names and Locations

Default Location File Name Component Firmware Name SYSnn SAM0815 ServerNet Switch (c7000 enclosure)

ME FPGA (see Caution below)

SYSnn SAM0437

ServerNet Switch (IOAM enclosure)

ME FPGA (see Caution below)

SYSnn SAM0789

VIO enclosure logic board ME FPGA for IME in G16SE

enclosures and VIO enclosures (see Caution below)

CAUTION: You should not use the Multi-Resource Actions dialog (in the OSM Service Connection) to updateME FPGAsimultaneously 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 theME FPGA Updateaction 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 supportedOAfirmware 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.

(25)

Table 4 Server Blade Firmware for All NonStop System Running J-Series Software Except for the NS2000 Series System

Product Description Firmware Name

Used to reset, halt, load, and dump a server blade. Delivered as an Independent Product on theNSCDVD.

Halted State Services firmware

Controller firmware for legacy I/O orSCSIdisks in G-series RVUs. ISP1040 firmware

Used during a system load. DISKBOOT firmware

Table 5 Blade Element Firmware for NonStop NS2000 Series Systems Product Description

Firmware Name

Used to reset, halt, load, and dump a blade element. Delivered as an Independent Product on theNSCDVD.

Halted State Services and HPI Loader T8004 Firmware

Controller firmware for legacy I/O orSCSIdisks in G-series RVUs. This firmware is packaged as part of the DVD containing T8004 and cannot be updated independently.

ISP1040 Firmware

Used during a system load. This firmware is packaged as part of the DVD containing T8004 and cannot be updated independently. DISKBOOT Firmware

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 Where Adapter Is Installed ServerNet Adapter

IOAM enclosure in a NonStop BladeSystem Fibre Channel ServerNet Adapter (FCSA)

IOAM enclosure in a NonStop BladeSystem Gigabit Ethernet 4-port ServerNet Adapter

(G4SA)

I/O enclosure in a NonStop S-series system connected to ServerNet switches in a NonStop BladeSystem c7000 enclosure

6763 Common Communication ServerNet Adapter (CCSA)

I/O enclosure in a NonStop S-series system connected to ServerNet switches in a NonStop BladeSystem c7000 enclosure

Token Ring ServerNet Adapter (TRSA)

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.

(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 showsDown-rev, update the firmware. The following example shows that the firmware is at an earlier version and needs to be updated:

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

(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

Latest NonStop T-Number and Firmware Level Firmware

ServerNet Adapter

T0630G06^AAU FCSA flash firmware

Fibre Channel ServerNet Adapter (FCSA)

T0612G06^AAB FCSA Flash Boot firmware

Fibre Channel ServerNet Adapter (FCSA)

T0613G06^AAS G4SA Boot firmware

Gigabit Ethernet 4-Port ServerNet Adapter (G4SA)

T0309G08^AAF SS7 firmware

6373 Common Communication ServerNet Adapter (CCSA)

Managing SWAN and SWAN 2 Concentrator Firmware

BothSWANand 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 atwww.hp.com/go/nonstop-docs.

(29)

Table 8 Updateable Firmware for the NonStop ServerNet 6770 and 6780 Cluster Switch File Names and Locations Tool Default Location File Name Component Firmware Name ServerNet Cluster 6780 Operations Guide SCF or OSM Service Connection SYSnn subvolume M2789 6780 Cluster

Switch logic board Router-2 ASIC* firmware ServerNet Cluster 6770 Hardware SCF or OSM Service Connection SYSnn subvolume M6770 6770 Cluster Switch Switch configuration

firmware Installation and

Support Guide

Managing CLIM Firmware and Software

If your system hasCLIMs 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 atwww.hp.com/go/ 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 thePrepare 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 thePrepare for Down System CLIM Firmware Updateaction, 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 selectingAll 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

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

Tool Default Location File Name Firmware Name Component DSM/SCM and SCF SYSnn subvolume C0309P00 SS7 Controller

firmware, required for CCSA

connectivity with S-series systems

OSM Service

Connection and OSM Low-Level Link SYSnn subvolume

SPCODE9 Service Processor

firmware, required to connect to the S-series I/O enclosure PMF and PMF2; IOMF

andIOMF2

(31)

3 Installation, Migration, and Fallback Considerations for

This RVU

See the Readme file and the appropriate softdocs for the latest information on any migration or configuration steps. Considerations in this chapter are categorized according to the RVU at which they were introduced.

J06.04

Compiling C++ Programs to Run on RVUs Earlier Than J06.04

Objects compiled by the J06.04 and later C++ compilers might require new functions that are in the current C++ Common Runtime Library but not in RVUs earlier than J06.04. 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 ignoreoption):

• 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 H06.14.

NOTE: If you are compiling for an H-series target system, nn must be between 08 and 14, inclusive, as the Runtime Library supports only RVUs H06.08 and later.

You can fix the problem by installing T2831H01^AAD (Common Runtime Library) or later on 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

TheCLIMis 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, seeChapter 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.

(32)

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 Linuxcat

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

J06.05

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.OSSINFILfile by changing the line

SERVER #ZPLS

to

* SERVER #ZPLS

NOTE: target-volumeis normally $SYSTEM.

NOTE: #ZPLS cannot be deleted from ZOSSSERV but can be