G06.24 Software Installation and Upgrade Guide Abstract This manual provides detailed procedures for upgrading an HP NonStop™ S-series server to the G06.24 release version update (RVU) from any G06.06 or later RVU. Product Version N.A. Supported Release Version Updates (RVUs) This publication supports the G06.24 RVU only.
Document History Part Number Product Version Published 528593-005 NA January 2005 528593-004 NA October 2004 528593-003 NA August 2004 528593-002 NA August 2004
G06.24 Software Installation and Upgrade Guide Glossary Index What’s New in This Manual xi Manual Information xi New and Changed Information Tables xi About This Manual xiii Who Should Use This Guide xiii What This Guide Does Not Cover xiii How This Guide Relates to Other Manuals Notation Conventions xv xiv 1. Overview of Installing G06.
Contents 1. Overview of Installing G06.24 (continued) 1. Overview of Installing G06.24 (continued) Do Not Move or Relicense Pathway Files 1-20 Secure SCF Product Modules (Gnn.nn) 1-21 Resecure Visual Inspect (Gnn.nn) 1-21 G06.24 Installation and Fallback Alerts for Products 1-21 4619 Disk Drives 1-22 6780 ServerNet Switch (G06.21) 1-22 Backup and Restore 2 (BR2) (G06.24) 1-23 C++ (G06.20) 1-23 DP2 (G06.16, G06.23, G06.24) 1-24 Gigabit Ethernet ServerNet Adapter (G06.
2. G06.24 Upgrade Checklists Contents Part I. Upgrade Tasks 2. G06.24 Upgrade Checklists G06.24 Upgrade Checklist 2-1 G06.24 Required Information Checklist 2-4 3. Installing SPRs Before Upgrading to the G06.
5. Installing the G06.24 RVU Contents 5. Installing the G06.24 RVU Alerts 5-1 Back Up Important Files 5-2 Receive New Software Into the Archive 5-3 Create a New Software Revision 5-8 Build and Apply the New Software Revision 5-13 Print Operator Instructions From the Target Interface (ZPHITI) Recovery for Problems Installing the G06.24 RVU 5-22 Cancel Pending Build/Apply Requests 5-22 5-19 6. Replacing the Disk Bootstrap Microcode (Pre-G06.06) 7.
. Updating Service Processor (SP) Firmware (continued) Contents 7. Updating Service Processor (SP) Firmware (continued) Using OSM and Downloading the SP Firmware File to the System Console (Optional) 7-28 Updating Firmware Using the OSM Low-Level Link Application (Optional) 7-30 8. Updating Processor Boot Code Before You Begin Updating the Boot Millicode 8-3 Check Processor Status 8-3 Verify Your TSM and OSM Versions 8-3 Verify Location and Version of Processor Boot Code 8-3 Method 1: Using G06.
11. Loading the G06.24 RVU Contents 11. Loading the G06.24 RVU Alerts 11-1 Halt the Processors 11-2 Replace Processor or Other System CRUs 11-3 System Load Using the TSM or OSM Low-Level Link 11-4 Reload the Remaining Processors (If Necessary) 11-6 Check the Status of the Processors 11-7 Recovery Operations for System Load 11-7 Performing a System Load From the Mirror System Disk The Reset Operation 11-8 11-7 12.
12. Resuming Normal Operations (continued) Contents 12. Resuming Normal Operations (continued) Upgrade the TNOS Server and TNOS Utility (Optional) 12-16 Part II. Fallback Tasks 13. Preparing to Fall Back Alerts 13-1 Summary of Fallback Tasks 13-2 Fallback Considerations for Specific Products DP2 13-3 DLL (Dynamic-Link Libraries) 13-3 DSM/SCM 13-3 Spooler 13-4 Open System Services (OSS) 13-4 OSM and TSM 13-4 SMF 13-4 SQL/MX 2.0 13-5 TMF 13-5 WAN Manager (T8365) 13-5 13-2 14.
15. Returning Firmware to Previous Versions (continued) Contents 15. Returning Firmware to Previous Versions (continued) Returning Bootcode Firmware to the Previous Version (Using OSM) 15-6 16. Running ZPHIRNM to Reactivate the Previous Software Revision Alerts 16-1 Drain the Spooler 16-1 Run ZPHIRNM 16-2 Using PREVIEW Mode 16-2 Run ZPHIRNM 16-2 Verify That ZPHIRNM Ran Successfully 16-3 17.
Contents A. Using DSM/SCM to Install SPRs (continued) A. Using DSM/SCM to Install SPRs (continued) Perform a System Load A-10 Reload the Processors (If Necessary) A-11 Start Your Applications and Processes A-11 B.
Contents C. Updating SWAN Concentrator CLIP Firmware C.
Tables Contents Tables Table 1-1. Table 1-2. Table 1-3. Table 1-4. Table 1-5. Table 1-6. Table 1-7. Table 1-8. Table 1-9. Table 2-1. Table 2-2. Table 3-1. Table 3-2. Table 3-3. Table 3-4. Table 4-1. Table 7-1. Table 8-1. Table B-1. G06.24 Updateable Firmware for Processors, SPs, and SCSI SACs 1-9 G06.24 Updateable Firmware for ServerNet Adapters 1-10 G06.24 Updateable Firmware for ServerNet WAN (SWAN and SWAN 2) Concentrators 1-11 G06.24 Updateable Firmware for the NonStop ServerNet Switch 1-11 G06.
Tables Contents G06.
What’s New in This Manual Manual Information G06.24 Software Installation and Upgrade Guide Abstract This manual provides detailed procedures for upgrading an HP NonStop™ S-series server to the G06.24 release version update (RVU) from any G06.06 or later RVU. Product Version N.A. Supported Release Version Updates (RVUs) This publication supports the G06.24 RVU only.
What’s New in This Manual New and Changed Information G06.
About This Manual This guide describes: • • Upgrading a single NonStop S-series server to the G06.24 release version update (RVU) of the HP NonStop Kernel operating system from any G06.06 or later G-series RVU, including installing DSM/SCM client software. Falling back from the G06.24 RVU to a previous (G06.06 or later) G-series RVU. If you are migrating from an RVU prior to G06.06, contact your service provider trained by HP.
About This Manual • • How This Guide Relates to Other Manuals Installing, configuring, and migrating to HP NonStop SQL/MX. The SQL/MX Installation and Management Guide for SQL/MX Release 2.0 describes step-bystep instructions for installing SQL/MX for Release 2.0, including fallback procedures. Installing and configuring the I/O Adapter module (IOAM) enclosure and its components. See your HP service provider.
Notation Conventions About This Manual • • • The NonStop S-Series Planning and Configuration Guide provides information for planning and configuring the installation of a NonStop S-series server. The NonStop S-Series Hardware Installation and FastPath Guide provides detailed instructions and checklists for installing NonStop S-series servers. The SQL/MX Installation and Management Guide for SQL/MX Release 2.0 describes step-by-step instructions for installing SQL/MX for Release 2.0.
General Syntax Notation About This Manual A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list may be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ [ [ K [ num ] -num ] text ] X | D ] address { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item.
Notation for Messages About This Manual Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In the following example, there are no spaces permitted between the period and any other items: $process-name.#su-name Line Spacing.
Notation for Messages About This Manual be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: proc-name trapped [ in SQL | in SQL file system ] { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed.
1 Overview of Installing G06.24 This section introduces the tools and requirements for: • • Upgrading a single NonStop S-series server to the G06.24 RVU from any G06.06 or later G-series RVU Falling back from G06.24 to a previous (G06.
Overview of Installing G06.24 TSM Client Applications To ensure that the OSM Notification Director runs as a persistent service: 1. 2. 3. 4. Select Start > Settings > Control Panel > Administrative Tools > Services. Select the OSM Notification Director from the list of Services. Right-click and select Properties. Select the Recovery tab and change the properties for First, Second and Subsequent failures to Restart the Service. 5. Click OK to apply the changes. TSM Client Applications Note.
Overview of Installing G06.24 HP NonStop Server Software Requirements HP NonStop Server Software Requirements You must install: • The newest TSM server (T7945ABN or later) SPR if you are installing NonStop S78000 and S88000 servers. For TSM, if you have to install the most recent server SPRs, follow the instructions in the appropriate softdocs.
Overview of Installing G06.24 • • HP NonStop Server Software Requirements SQL/MX Release 2.0 fallback SPRs. See Section 3, Installing SPRs Before Upgrading to the G06.24 RVU. A D46 product version of DSM/SCM on your host system before you install the SUT. Appendix B, Installing the Latest DSM/SCM SPRs and Client Software describes how to restore from tape and install the recommended D46 SPR of DSM/SCM. The D46 DSM/SCM client and server version enable you to manage OSS files. Note.
Overview of Installing G06.24 DSM/SCM and the G06.24 RVU DSM/SCM and the G06.24 RVU Starting with the G06.18 RVU, a new configuration file, A7CINFO, is introduced for the managing of OSS files. To manage OSS files, you must install the T6031 D46 PVU on the host system before receiving the SUT. The corresponding client version of the software must also be installed. To upgrade the DSM/SCM client, the DSM/SCM client version must be downloaded from the ZDSMSCM subvolume.
Overview of Installing G06.24 Managing Microcode and Firmware 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 request is finished, a snapshot is automatically created and returned to the Host. 4.
Overview of Installing G06.24 Updating Firmware Bootstrap Microcode Update Requirements for the G06.24 RVU The disk and tape bootstrap programs (T8494) are unchanged in G06.24. A new disk bootstrap program (T8494AAA) became available in G06.06. Revive your mirrored disk as soon as possible after performing a system load.
Overview of Installing G06.24 Updating Firmware The ServerNet adapters are: • ATM3SA • CCSA • E4SA • FESA • GESA • TRSA • G4SA • ServerNet/FX and ServerNet/FX2 • FCSA (ServerNet I/O adapter) For more information, see the adapters’ respective installation and support guides. Firmware Updates and DSM/SCM (ZPHITI) The DSM/SCM Target Interface (ZPHITI) provides operator instructions that inform you if any firmware needs to be updated before you run the ZPHIRNM (rename) program.
Updating Firmware Overview of Installing G06.24 You must use OSM to update firmware for the HP NonStop Cluster 6780 Switch. For information on using OSM to update firmware, see the OSM online help. Note. When migrating to G06.24 from an RVU prior to G06.08, update SCSI boot code after the system load. Update SP and processor boot code before performing the system load of G06.24. Table 1-1 lists the updateable firmware for processors, SPs, and SCSI SACs. Table 1-1. G06.
Updating Firmware Overview of Installing G06.24 Table 1-2 lists the product numbers and updateable firmware for all ServerNet adapters that are installed on S-series servers and other modules connected to S-series servers. Table 1-2. G06.
Updating Firmware Overview of Installing G06.24 Table 1-3. G06.
Updating Firmware Overview of Installing G06.24 Table 1-5 lists the product number and updateable firmware information for the IOAM Maintenance Entity and FCSA. Check with your HP service provider for more information. Table 1-5. G06.
Overview of Installing G06.24 Investigating a New RVU Investigating a New RVU Several resources are available to help you plan for installing a new RVU: • • • • • The Release Version Update Compendium provides highlights of the new products and features for each G-series RVU. It also discusses the effect these changes have on installation and configuration, operations and management, data files, applications, and networks.
Installing a New RVU Overview of Installing G06.24 Table 1-6. Tasks and Tools for Installing the G06.24 RVU (page 1 of 2) To Perform This Task... Use This Tool... Documented in... 1. Install a D46 product version of DSM/SCM and fallback/interoperability SPRs. HP recommends that you install the D46 SPR on the host and on the client. You must also install the SWID product T9298D40^AAK if you are running an RVU before G06.20.
Upgrading NonStop S-Series Servers Overview of Installing G06.24 Table 1-6. Tasks and Tools for Installing the G06.24 RVU (page 2 of 2) To Perform This Task... Use This Tool... Documented in... 11. Update EMS template files (if necessary). INSTALL^TEMPLATES TACL macro If Running INSTALL^TEMPLATES Is Required on page A-7 12. Halt the processors. TSM Low-Level Link Application or OSM LowLevel Link Halt the Processors on page 11-2 13.
Overview of Installing G06.24 Installing an IOAM Enclosure and Other Components After you change the CONFTEXT file, you must perform all required DSM/SCM requests to create a new SYSnn, including the new processor type. Perform a system load of the new SYSnn after the new hardware is installed. Caution. Never load the new SYSnn that contains the new processor type into your current processors. Otherwise, a system outage will result, and you will have to fall back to your previous RVU.
Overview of Installing G06.24 • • Falling Back to the Previous RVU You must install the IOAM enclosure as group 11, 12, 13, 14, or 15. The presence of an IOAM enclosure in your system requires that certain other groups be left empty. For more information, contact your service provider. You must isolate SWAN adapters on your system before you install an IOAM enclosure. For more information, contact your service provider.
Overview of Installing G06.24 Using DSM/SCM FALLBACK and CLEANOSS Macros Using DSM/SCM FALLBACK and CLEANOSS Macros If you need to fall back from an RVU that does not have installed a D46 DSM/SCM PVU, you must run the DSM/SCM FALLBACK macro from the ZDSMSCM subvolume. The interactive macro must be run by the DSM/SCM owner or by super ID (255,255). The FALLBACK macro reverts the DSM/SCM Host or Target, or both, database back to a pre-D46 state for use by a pre-D46 product version of DSM/SCM.
Overview of Installing G06.24 DSM/SCM Client and Server Compatibility 11:43:03 AM 10/27/03 $Z420 DSM/SCM: *5305* Server Class TA-001 of PATHMON \TINY.$YPHI activity id \TINY211933793397226152, activity code 20, planner id SUPER.SUPER in stage 202: EMSTEXT -- No template and no TEXT token for event. SSID = TANDEM.DSMSCM.D30 Event number = 5305 Subject = \TINY211933793397226152 See the DSM/SCM Messages Manual for more information on what message should be displayed.
Resecuring and Licensing Requirements Overview of Installing G06.24 Table 1-7. Tasks and Tools for Falling Back to the Previous RVU To Perform This Task... Use This Tool... Documented in This Section... 1. Submit a backout request. DSM/SCM Target Interface (ZPHITI) Section 14, Backing Out the DSM/SCM Revision 2. Return the firmware back to the prevision versions (if necessary). TSM Service Application Section 15, Returning Firmware to Previous Versions OSM Service Connection (if installed) 3.
Overview of Installing G06.24 Secure SCF Product Modules (Gnn.nn) Table 1-8. Pathway Licensing Errors Licensing Error Description 1163 The PATHMON process could not start because it could not confirm that either the TS/MP product or the Pathway/iTS product is licensed for your site. 1164 A command to a remote system requires the TS/MP or the Pathway/iTS product, but the PATHMON process cannot confirm that the required product is licensed for the remote system.
Overview of Installing G06.24 • • • • • • • • • • • • • • • • • • • • 4619 Disk Drives Gigabit Ethernet ServerNet Adapter (G06.16) on page 1-24 Minimum Memory Requirements (G06.16) on page 1-24 OSM Configuration and Fallback (G06.08 to G06.24) on page 1-25 OSS (G06.12 through G06.24) on page 1-25 ° ° Open System Services (OSS) and DSM/SCM (T6031D46 PVU) on page 1-27 OSS EasySetup (T0585) (G06.16, G06.23) on page 1-28 NonStop SQL/MP on page 1-28 NonStop SQL/MX Release 2.0 (G06.23 and G06.
Overview of Installing G06.24 Backup and Restore 2 (BR2) (G06.24) Backup and Restore 2 (BR2) (G06.24) Backup and Restore 2.0 supports OSS and SQL/MX files and consists of these major components: • • • • Backup and Restore Command Interface (BRCOM) (T2721) Data Service (T2750) Data Management Application (DMA) (T2749) Tape Service (T2722) For more information on these SPRs, see the Interactive Upgrade Guide. These Backup and Restore 2.0 SPRs that support OSS files are included on the G06.
Overview of Installing G06.24 DP2 (G06.16, G06.23, G06.24) DP2 (G06.16, G06.23, G06.24) If you set the AUDITTRAILBUFFER or the SQLMXBUFFER attribute to 128 or more, you need to reset these values to 0 before falling back to G06.16 or an earlier RVU. If you fail to do so, TMF might not start, or a disk volume might go offline. You can recover from this situation by using the SCF ALTER command. See the Interactive Upgrade Guide for details. If you are planning to use SQL/MX Release 2.
Overview of Installing G06.24 OSM Configuration and Fallback (G06.08 to G06.24) OSM Configuration and Fallback (G06.08 to G06.24) For fallback issues, see the OSM Migration Guide.
Overview of Installing G06.24 • • OSS (G06.12 through G06.24) Beginning with the G06.18 RVU, all OSS SUT-based products with pax files must have the A7CINFO file in their DSVs to be installed by DSM/SCM. Before installing the SUT: ° Check the Interactive Upgrade Guide for DSM/SCM support and other new features and possible migration issues. ° Check the appropriate softdoc for the OSS product. ° Check that all OSS file sets used by DSM/SCM for OSS file installation are mounted and started.
Overview of Installing G06.24 OSS (G06.12 through G06.24) Open System Services (OSS) and DSM/SCM (T6031D46 PVU) Starting with the G06.18 RVU, all OSS SUT-based products with pax files must have the A7CINFO file in their DSVs to be installed by DSM/SCM. Check the Interactive Upgrade Guide or the softdoc corresponding to the OSS products to ensure that the A7CINFO file is present. If the OSS product is released without the A7CINFO file, you can still install the product by using PINSTALL or COPYOSS.
Overview of Installing G06.24 NonStop SQL/MP OSS EasySetup (T0585) (G06.16, G06.23) 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. OSS EasySetup requires the process $NULL and the installation of SPI template files.
Overview of Installing G06.24 NonStop SQL/MX Release 2.0 (G06.23 and G06.24) SQL/MX Release 2.0 delivers the newly architected, standards-based SQL/MX tables for NonStop servers. SQL/MX Release 2.0 provides general availability support for operations against SQL/MP tables. Support for SQL/MX tables is not included in the G06.24 RVU. The function, when available, will be shipped as SPRs and is planned to be compatible with G06.23 and G06.24. Migration Considerations for SQL/MX Release 2.
Overview of Installing G06.24 • • • NonStop SQL/MX Release 2.0 (G06.23 and G06.24) If you modify or create new SQL/MP aliases, defaults, or stored procedures in Java (SPJs) in the SQL/MX Release 2.0 environment, there are no automated tools for moving the associated SQL/MX metadata back to SQL/MP metadata tables. Moving metadata will require you to execute SQLCI commands such as CREATE MPALIAS, CREATE PROCEDURE, and INSERT INTO DEFAULTS after reinstalling SQL/MX Release 1.8.
NonStop SQL/MX Release 2.0 (G06.23 and G06.24) Overview of Installing G06.24 2>$system.zutil.dircheck delete name $data08.zsdm819j.wdxhp600 System: \MOLE *WARNING* *WARNING* PID: (0, 72) 8-Apr-2004 18:06:57 SQL Catalog will not be updated when SQL labels are deleted. Extents are lost when file/table labels are deleted. Note. When using DIRCHECK, remember: • • You must be the super ID (255,255). The DIRCHECK DELETE command deletes any internal labels associated with a specified file.
NonStop Processor Multifunction (PMF) CRUs (G06.08 through G06.24) Overview of Installing G06.24 NonStop Processor Multifunction (PMF) CRUs (G06.08 through G06.24) If you upgrade to NonStop PMF CRUs while installing G06.24 and have to return to an RVU prior to G06.24, review Table 1-9 to see if you have to remove PMF CRUs: Table 1-9. Upgrading to NonStop S-Series CRUs and Falling Back NonStop PMF CRU RVU Action S7400 G06.08 S7400 PMF CRUs must be removed; these PMF CRUs are supported in G06.
Overview of Installing G06.24 Spooler (G06.00 through G06.19) Spooler (G06.00 through G06.19) If your current product version of spooler is T9101D41 ADM or later, you do not need to restore copies of both the control file and the collector data files if you must back out of the new RVU. All versions of T9101D41, starting with T9101D41 ADM, contain Version 5 of the spooler control file and are compatible with the T9101D46 and D48 product versions of spooler.
Overview of Installing G06.24 SCF Storage Subsystem (Online Disk Remirroring) (G06.21) Upon receipt of 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 any active jobs and then stops. After all collectors and print processes have stopped, the supervisor process stops itself.
Overview of Installing G06.24 SWID (T9298D40^AAK) (G06.20) SWID (T9298D40^AAK) (G06.20) SWID is the software identification tool invoked by the SYSGENR program that audits file identification information about your software. If you are currently on a post G06.19 RVU (G06.20 or G06.21 RVU), you do not need to restore and receive the new SWID PVU before you install the G06.24 SUT. If you are on a pre-G06.20 RVU, you must restore and receive the new SWID PVU before you install the G06.24 SUT.
Overview of Installing G06.24 Service Processor (SP) Firmware (G06.08 through G06.24) TSM does not support or adequately support these new features, beginning with the G06.21 RVU: • • • • • • • Online Disk Remirroring (FDR) (G06.21). Only OSM automatically recognizes online remirrored disks. TSM can recognize online remirrored disks only if $ZTSM is aborted and then restarted. HP NonStop ServerNet cluster (G06.21).
Overview of Installing G06.24 SCF for Data Alignment (G06.17) SCF for Data Alignment (G06.17) Starting with the G06.17 RVU, three attributes are added to the ALTER SUBSYS command of the Subsystem Control Facility (SCF). These attributes are intended to help application programmers find and correct misaligned data in their programs. These data alignment errors might lead to incorrect or unpredictable results.
Overview of Installing G06.24 NonStop TCP/IPv6 (G06.20, G06.22, G06.23, G06.24) NonStop TCP/IPv6 (G06.20, G06.22, G06.23, G06.24) With the introduction of NonStop TCP/IPv6 in the G06.20 RVU, all NonStop TCP/IPv6 protocol files are located in $SYSTEM.ZTCPIP subvolume. If you are upgrading from a pre-G06.20 RVU, back up your NonStop TCP/IP configuration files before running ZPHIRNM. (HP recommends backing up your TCP/IP configuration files before running ZPHIRNM even if you are on a G06.20 or later RVU).
Overview of Installing G06.24 TNOS Server and TNOS Utility (G06.17 through G06.24) To establish complete TMF file recovery protection for your SQL/MX metadata tables, update your TMF online dump (and Backup) scripts to include the names of all SQL/MX metadata tables, including those that are SQL objects and their resource forks. The TMFCOM DUMP FILES and RECOVER FILES commands support all the new SQL/MX metadata tables (using their Guardian names).
Overview of Installing G06.24 Visual Inspect (G06.20) Post installation instructions can be found in the appropriate PVU softdoc. New EMS templates are required for the T8666D35 PVU. See support note S02075B for details concerning TNOS and data alignment problems. Visual Inspect (G06.20) G06.20 includes the Inspect subsystem (T9226G06) and the Visual Inspect server (T9756AAH) that support PIC programs and DLLs. This version of the server requires version 2.4 of the Visual Inspect client (T7877AAD).
Overview of Installing G06.24 X25AM X25AM A new SCF line modifier, EMSFORFRMR, is provided so that an EMS message is displayed when a link reset occurs from a Frame Reject (FRMR) condition on an X25AM line. The modifier accepts values in the range from 0 to 200. Configure this SCF modifier with a nonzero value to enable the generation of an EMS message during an FRMR condition. (By default, the feature is disabled.
Overview of Installing G06.24 G06.
Part I. Upgrade Tasks Part I describes the tasks for upgrading a single NonStop S-series server to the G06.23 RVU, as follows: • • • • • • • • • • • • Section 2, G06.24 Upgrade Checklists Section 3, Installing SPRs Before Upgrading to the G06.24 RVU Section 4, Preparing to Upgrade the Server Software Section 5, Installing the G06.24 RVU Section 6, Replacing the Disk Bootstrap Microcode (Pre-G06.
Part I. Upgrade Tasks G06.
2 G06.24 Upgrade Checklists Use the checklist in Table 2-1 as you perform the tasks required to upgrade to the G06.24 RVU and the checklist in Table 2-2 to record the information needed when performing these tasks. Task durations are included in Table 2-1. Most of these baseline durations were established on an NonStop S72002 server running the G06.12 RVU under minimal load (one user).
G06.24 Upgrade Checklist G06.24 Upgrade Checklists Table 2-1. G06.24 Upgrade Checklist (page 2 of 3) Task Description Minimum Duration Documentation 10. Build and apply G06.24 software revision 2 hours with OSS files Build and Apply the New Software Revision on page 5-13 11. Print the DSM/SCM Operator Instructions <1 minute Print Operator Instructions From the Target Interface (ZPHITI) on page 5-19 12. Install and configure the OSM SPRs or TSM SPRs (optional) 0.
G06.24 Upgrade Checklist G06.24 Upgrade Checklists Table 2-1. G06.24 Upgrade Checklist (page 3 of 3) Task Description Minimum Duration Documentation 27. Configure the Spooler (if necessary) 2 minutes Configure the Spooler on page 12-9 28. Start system and application software 11 minutes Start User and System Applications on page 12-10 29.
G06.24 Required Information Checklist G06.24 Upgrade Checklists G06.24 Required Information Checklist Table 2-2. G06.24 Required Information Checklist Type of Information Value Volume where SYSnn subvolumes are located (usually $SYSTEM) Current SYSnn (before upgrading to G06.24) SYSnn created during G06.
3 Installing SPRs Before Upgrading to the G06.24 RVU This section describes the SPRs you should install on your current RVU before you upgrade to the G06.24 RVU. SPRs provide new features between RVUs or correct previous software problems. Alerts • • • • • • Before installing an SPR: ° Do not apply any SPR unless you verify that you can apply it to your current G-series RVU.
Installing SPRs Before Upgrading to the G06.24 RVU SPRs Required Before Upgrading SPRs Required Before Upgrading Depending on which RVU you are currently running, a number of SPRs must be installed on your current RVU before you upgrade to the G06.24 RVU: • • D46 DSM/SCM: At least a D46 DSM/SCM product version must be installed on the host system before the site update tape (SUT) can be received into the archive.
Installing SPRs Before Upgrading to the G06.24 RVU Summary of the SPR Installation Procedure Summary of the SPR Installation Procedure 1. Use Scout to verify that you can apply the DSM/SCM SPR to your current G-series RVU. 2. Use DSM/SCM to install the required SPRs. For detailed instructions, see Appendix A, Using DSM/SCM to Install SPRs. 3. If necessary, use TSM to update firmware (DSM/SCM notifies you if firmware needs updating). 4.
Installing SPRs Before Upgrading to the G06.24 RVU Determining Your Current DSM/SCM Version Determining Your Current DSM/SCM Version To verify which 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.
Installing SPRs Before Upgrading to the G06.24 RVU DSM/SCM Client and Server Compatibility DSM/SCM Client and Server Compatibility The D46 DSM/SCM client is backward compatible with other DSM/SCM product versions (backward compatible to T6030D30/T6031D30 [AAO and later]). Table 3-1. DSM/SCM Client and Server Compatibility This version of the DSM/SCM Planner Interface... With this version of DSM/SCM server software...
Installing SPRs Before Upgrading to the G06.24 RVU Fallback SPRs Fallback SPRs You must install fallback SPRs on your system before upgrading to the G06.24 RVU, or fallback is not possible. NonStop SQL/MP Fallback SPRs As of G06.13, the NonStop SQL/MP Format 2 partitions program provides the ability to extend the existing 2 GB partition limit up to a maximum of 1 terabyte (TB). No fallback SPRs are available to fall back to pre-G06.03 RVUs. Fallback SPRs are available for G06.03 through G06.13.
Installing SPRs Before Upgrading to the G06.24 RVU Interoperability SPRs Table 3-3. SPRs Required for NonStop SQL/MX Release 2.0 Fallback Product SPR (or Superseding) Notes DP2 T9053AOY or T9053AOZ If applied, a system load is required before upgrading to the new RVU. The SPRs are applicable to RVUs G06.13 through G06.22. See DP2 (G06.16, G06.23, G06.24) on page 1-24.
Installing SPRs Before Upgrading to the G06.24 RVU NonStop SQL AUDSERV Interoperability SPRs Table 3-4. RDF Interoperability SPRs If a primary or backup node within the RDF environment is running this RVU... And any other node in the RDF environment is upgraded to a G06.00 or later or D46.00 or later RVU, install this (or a superseding) SPR on the down-level node... D32.00 through D39.00 T5864ABD D42.00 through D45.00 T5864ABE G02.00 through G05.
Installing SPRs Before Upgrading to the G06.24 RVU Determining the Current Version of OSM Configuring OSM Server Settings For detailed information about configuring OSM server processes, see the OSM Migration Guide. Determining the Current Version of OSM To determine the current product version of OSM for both the client portion and server, select About OSM from the OSM Service Connection Help menu. (You must be logged on to the OSM Service Connection.
Installing SPRs Before Upgrading to the G06.24 RVU TSM Server and Client Compatibility SPRs TSM Server and Client Compatibility SPRs Note. Starting with the G06.24 RVU, the CSSI Web snapshot is no longer provided on the installer CD, but the CSSI website can be accessed from the NonStop Technical Library (NTL). See the NonStop System Console Installer Guide for more information.
4 Preparing to Upgrade the Server Software Use this section to perform these tasks before you upgrade your server software: 1. 2. 3. 4. Save the Current Configuration File (CONFxxyy) Upgrade the System Console Software Verify System Operations Record the Current SYSnn 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.
Preparing to Upgrade the Server Software Upgrade the System Console Software If you specify a configuration file that already exists, SCF asks 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.
Preparing to Upgrade the Server Software Verify System Operations . Note. New system console requirements must be met if you decide to use OSM as your default client whether you migrate to Windows XP Professional. See the OSM Migration Guide or the NonStop System Console Installer Guide for more information. HP recommends that you upgrade to Microsoft Windows XP Professional first before upgrading your NonStop system console.
Preparing to Upgrade the Server Software Check Processor Status (Using either TSM or OSM) Check Processor Status (Using either TSM or OSM) Check Processor Status (Using TSM) Verify that the NonStop Kernel is running in all processors: 1. Log on to the TSM Low-Level Link Application and perform a System Discovery. 2. From the toolbar, click Processor Status. The Processor Status dialog box appears. The Processor Status for all processors should be Executing NonStop OS.
Preparing to Upgrade the Server Software Check System Enclosure Components (Using TSM) Check System Enclosure Components (Using TSM) Verify the operational status of the components in each system enclosure: 1. Log on to the TSM Service Application. 2. Check for alarm conditions in the tree pane of the management window. For example: VST200.vsd G06.
Preparing to Upgrade the Server Software Check System Enclosure Components (Using TSM) 3. Select an item in the tree pane that shows alarm conditions, and then click the Alarms tab to view the alarms associated with the selected item. • • If a yellow triangle appears over an enclosure diagram, determine the cause of the problem. Correct the problem if possible. Determine if you can proceed without affecting the installation of software.
Preparing to Upgrade the Server Software Check System Enclosure Components (Using TSM) Check System Components (Using OSM) Note. Do not launch the OSM Service Connection if you do not already have OSM server processes configured. If OSM is not installed, use TSM to migrate to the G06.24 RVU. 1. Log on to the OSM Service Connection. See the OSM Migration Guide if you have any problems accessing OSM.
Preparing to Upgrade the Server Software ° Check System Enclosure Components (Using TSM) If you are on an earlier OSM Service Connection version, remember to use the OSM Refresh, Reanalyze, or Rediscover actions for updating interface display for the desired resource objects. 2. The System Status window indicates the overall health of a system by the color of the system icon. Green indicates that the overall health is fine; yellow indicates a possible system problem.
Preparing to Upgrade the Server Software Check Critical System Processes 3. Select an item in the tree pane that shows alarm conditions, and then click the Alarms tab to view the alarms associated with the selected item. • • • If a yellow triangle appears over an enclosure diagram, determine the cause of the problem. Expand the tree. Correct the problem if possible. Determine if you can proceed without affecting the installation of software.
Check the Status of the ServerNet Addressable Controllers (SACs) Preparing to Upgrade the Server Software Check the Status of the ServerNet Addressable Controllers (SACs) Check the status of the SACs in the ServerNet LAN Systems Access (SLSA) subsystem using SCF: 5> scf SCF - T9082G02 - (15APR98) (04MAR98) - 02/23/99 14:11:31 System \ELI Copyright Tandem Computers Incorporated 1986 - 1998 (Invoking \ELI.$SYSTEM.SUPER.SCFCSTM) 1-> assume $zzlan $ZZLAN 2-> status sac * SLSA Status SAC Name $ZZLAN.MIOE0.
Check the Swap File Configuration Preparing to Upgrade the Server Software 177 *STARTED STARTED *STARTED STARTED PID 0,291 PID 1,276 3. If the $SYSTEM, DSM/SCM, and Archive volumes are not listed in the display, contact your service provider. 4. Verify that the primary path, backup paths, mirror path, and mirror backup path are started for the mirrored $SYSTEM volume. If any paths are stopped, start them. 5.
Preparing to Upgrade the Server Software Check the Swap File Configuration $AUDIT0.ZSYSSWAP.CPU3A Extent Size 128 disk pages MaxExtents 128 File Size 32 MB CPU 3 Threshold Default . . . 2. Verify that each processor in the system has a configured swap file of at least 256 MB in the minimum for any G-series system. Depending on how many processes you have, your system configuration might require more swap space. For each processor, configure at least twice as much swap space as there is memory.
Check the Status of the Spooler Collector Preparing to Upgrade the Server Software . . Check the Status of the Spooler Collector Check that the spooler collector is active and not 100 percent full. At a TACL prompt, start SPOOLCOM and issue a COLLECT, STATUS command. For example: 1> spoolcom $spls; collect, status COLLECT $S STATE ACTIVE FLAGS 3 , CPU 1 PRI 154 UNIT 4 DATA FILE $OPS0.SPL.
Preparing to Upgrade the Server Software Record the Current SYSnn Record the Current SYSnn Identify and record the current SYSnn subvolume on your system. You will have to specify this SYSnn subvolume if you need to fall back from the G06.24 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 0,0 PFR %WT Userid Program file Hometerm 201 P R 000 255,255 $SYSTEM.SYS01.OSIMAGE $YMIOP.#CLCI Swap File Name: $SYSTEM.
5 Installing the G06.24 RVU Installing a new RVU involves these DSM/SCM tasks: 1. Receive New Software Into the Archive 2. Create a New Software Revision 3. Build and Apply the New Software Revision Alerts Do not use this procedure to upgrade more than one NonStop S-series server at a time or to install SPRs. Before you install the G06.24 RVU, these requirements must be met: • Always install the latest D46 software product version (SPR) of DSM/SCM and the DSM/SCM client before receiving the SUT.
Installing the G06.24 RVU • • • • Back Up Important Files 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. Check that the OutsideView Startup TACL ($YMIOP.#CLCI) and EMS Event Stream windows are open. These windows must remain open while DSM/SCM is performing a Build/Apply; otherwise, Build/Apply errors result.
Installing the G06.24 RVU Receive New Software Into the Archive Receive New Software Into the Archive Receiving software into the Archive might take several hours. To receive the SUT containing the G06.24 RVU into the DSM/SCM Archive: 1. Start TMF and DSM/SCM if they are not already running. For example: > TMFCOM START TMF > VOLUME $dsmscm_vol.ZDSMSCM > RUN STARTSCM 8> startscm DSM/SCM Process Startup Function - STARTSCM - T6031D46 - (31MAR2003) Copyright Hewlett Packard Development Company L.P.
Installing the G06.24 RVU Receive New Software Into the Archive vst500.vsd 4. In the Software in Archive dialog box, click Receive software. The Receive Software Request dialog box appears. For example: VST505.vsd G06.
Installing the G06.24 RVU Receive New Software Into the Archive 5. In the Receive Options group box, do the following, depending on your system environment: ° ° Select Receive only changed files if you do not want to manage OSS files. Select Receive all files if you want to manage OSS files. If this option is selected, the receive will take about an hour or two even if you have recently upgraded to a new RVU. 6. Under Software name, select Provided by planner and enter a name for the RVU. 7.
Installing the G06.24 RVU Receive New Software Into the Archive 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 new reel (or cartridge on a nonautoloading drive) of the SUT needs to be mounted. EMS messages are displayed in the following windows: ° ° The OutsideView EMS Event Stream window The EMS Events window displayed by DSM/SCM when you click Show EMS events from the Status window G06.
Installing the G06.24 RVU Receive New Software Into the Archive You can also check the Requests window to ensure that the request is finished. (Select Requests>Requests list). For example: VST525.vsd 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: vst556.vsd G06.
Create a New Software Revision Installing the G06.24 RVU 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 6 after you are in the Planner Interface Configuration Revisions window.
Create a New Software Revision Installing the G06.24 RVU 2. In DSM/SCM, the Planner Interface, in the Configuration Revisions window, select the target configuration. 3. Select Maintain>Target Maintenance>Modify. a. Select the Manage OSS Files option. Manage OSS Files VST447.vsd b. Click Output to view the default ouput values. c. Enter default output values in the data fields as needed. d. Click OK. G06.
Installing the G06.24 RVU Create a New Software Revision . Note. If you receive this error message stating that the current target is pre-D46, you can continue with the installation if you are certain that you have installed the DSM/SCM T6031D46 PVU or later SPR. To check the correct product version: 1. Use the following DSM/SCM VPROC commands: > volume $dsmscm_vol.ZDSMSCM > vproc taexe > vproc cbexe 2. Log on to TI by running ZPHITI (page 5-19). The current target version appears. > RUN ZPHITI 3.
Installing the G06.24 RVU Create a New Software Revision b. Add a description describing the new software revision (such as G06.24 SUT) and click OK. c. On the Software in Archive window, select the G06.24 RVU that was just received into the archive and click Copy to. VST559.vsd 7. Click Continue when the Confirmation message appears: The current contents of the new revision will be deleted. Products named in this target’s custfile will be required for the new revision. vst560.
Installing the G06.24 RVU Create a New Software Revision An example of a product version mismatch might occur when T9225D46 (TNS/R C++ Compiler) is installed using DSM/SCM. If you are not currently running TT9225D46, the Planner Interface displays a "Version Mismatch" message to indicate that the version of this SPR is different from the version of the base component. Click Continue.
Installing the G06.24 RVU Build and Apply the New Software Revision vst555.vsd 9. 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. Note. The Activation Package contains installation instructions for the pax files of those OSS products that contain A7CINFO files in their distributed subvolumes.
Installing the G06.24 RVU Build and Apply the New Software Revision Note. You might receive this message: The message is warning you that the last DSM/SCM snapshot was created by a pre-T6031D46 version of DSM/SCM, which would be the case if you have not installed the T6031D46 product version. If you are certain that you are on a D46 PVU of DSM/SCM, ignore the message and continue with the G06.24 installation.
Installing the G06.24 RVU Build and Apply the New Software Revision 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. (For other ways to determine the SYSnn, see Determine the Current SYSnn on page A-3.) > fileinfo $system.*.
Build and Apply the New Software Revision Installing the G06.24 RVU 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.
Installing the G06.24 RVU Build and Apply the New Software Revision 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.
Installing the G06.24 RVU • • Build and Apply the New Software Revision 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. G06.
Print Operator Instructions From the Target Interface (ZPHITI) Installing the G06.24 RVU Print Operator Instructions From the Target Interface (ZPHITI) Print the operator instructions that you edited in Step 6 on page 5-16. 1.
Installing the G06.24 RVU Print Operator Instructions From the Target Interface (ZPHITI) 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.
Installing the G06.24 RVU Print Operator Instructions From the Target Interface (ZPHITI) An example might look like this: Activation Instructions for \WARRIOR DEFAULT 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 TMDS (or TSM for S-Series) to check firmware and perform firmware updates.
Installing the G06.24 RVU Recovery for Problems Installing the G06.24 RVU Recovery for Problems Installing the G06.24 RVU If you receive an error indication in the Requests, Status, or EMS Events windows, you might have to reinitiate the Build/Apply. See the DSM/SCM Messages Manual to determine the nature and severity of the problem. Cancel Pending Build/Apply Requests Note.
Installing the G06.24 RVU Cancel Pending Build/Apply Requests d. Click OK. You must always use the new software input instead of the previously received software input brought into the Archive. G06.
Installing the G06.24 RVU Cancel Pending Build/Apply Requests G06.
6 Replacing the Disk Bootstrap Microcode (Pre-G06.06) As of the G06.06 RVU, a new disk bootstrap program is available. If you are migrating to the G06.24 RVU from an RVU prior to G06.06, you must replace the existing disk bootstrap microcode with this new version, as described in this section. If you update the disk boot code, you must down the mirrored disk. The mirror should be revived as soon as possible after performing a system load.
Replacing the Disk Bootstrap Microcode (PreG06.06) G06.
7 Updating Service Processor (SP) Firmware Note. Update SP firmware only: • • If instructed to do so by DSM/SCM If you are not replacing the PMF CRUs in your system while migrating to the G06.24 RVU See TSM or OSM online help for information about updating SP firmware when replacing an I/O multifunction (IOMF) CRU or processor multifunction (PMF) CRU. To update SP firmware using OSM, if it is installed and configured, see Updating SP Firmware Using the OSM Service Connection on page 7-20.
Updating Service Processor (SP) Firmware Alerts Alerts • • • • • • • • • When using the TSM Service Application to update the service processor firmware, use the Firmware Update dialog box. Do not use the Single SP Firmware dialog box unless instructed to do so to recover from a failed service processor update. Check that no other service processor firmware updates are in progress before updating service processor firmware.
Before You Begin Updating Service Processor (SP) Firmware Before You Begin 1. Verify that the system is up with at least one processor running the NonStop Kernel. 2. Verify that you know the SYSnn for the new RVU and for your current RVU. See Check Processor Status (Using either TSM or OSM) on page 4-4. • • The SYSnn for your current RVU was determined in the Record the Current SYSnn procedure on 4-14. The SYSnn for the G06.
Determine the Current and New Versions of SP Firmware Updating Service Processor (SP) Firmware Determine the Current and New Versions of SP Firmware When updating SP firmware, you need: • • The SP firmware version for your current RVU to determine that the SPs are in a known, good state before you begin the SP firmware update The SP firmware version for the G06.
Updating Service Processor (SP) Firmware Verify That Your Current RVU Is Running the Correct Version of SP Firmware (Using TSM) Verify That Your Current RVU Is Running the Correct Version of SP Firmware (Using TSM) 1. Log on to the TSM Service Application. 2. Select Display>SP Actions. The Service Processor Actions dialog box appears. Wait for the firmware version of each SP to appear (this might take several minutes). 3.
Updating Service Processor (SP) Firmware Download the SP Firmware File to the System Console 6. Verify that the SP reset finishes successfully. Wait until the display in the Action Status box shows that the reset is Completed. If the Action Status box shows that the reset has failed or if the completed status does not appear, contact your service provider. 7. Repeat Steps 3 through 6 for the X-fabric service processors.
Updating Service Processor (SP) Firmware Download the SP Firmware File to the System Console vst642.vsd 6. Click OK. The Browse window closes, and an IXF - Receive dialog box appears, showing the download progress of the spntcde9 file. The download should take around 5 minutes. 7. When the IXF - Receive dialog box indicates that the transfer is finished, click End Transfer. G06.
Updating Service Processor (SP) Firmware Update SP Firmware Using the TSM Service Application Update SP Firmware Using the TSM Service Application 1. If necessary, log on to the TSM Service Application. 2. If necessary, display the Service Processor Actions dialog box, either by selecting SP Actions in the toolbar or by selecting Display>SP Actions. vst630.vsd G06.
Updating Service Processor (SP) Firmware Update SP Firmware Using the TSM Service Application 3. Using the Service Processors (SPs) list, determine which fabric (X or Y) contains the secondary master service processor. (You must choose this fabric when you begin updating service processor firmware): • • If an asterisk appears on the line for GRP-1.MOD-1.SLOT-50, then the Y fabric contains the secondary master service processor; choose the Y fabric for the remaining steps in this procedure.
Updating Service Processor (SP) Firmware Update SP Firmware Using the TSM Service Application 9. Enter the new file location. Use the $SYSTEM.SYSnn subvolume created during the most recent DSM/SCM Build/Apply. For example: Specify Firmware File Location Enter firmware file location and name: $volume.subvolume $system.sys02 File name SPCODE9 VST646.vsd 10. Click OK. 11. Click Yes when a message appears, warning that you have specified a nonstandard firmware file location.
Updating Service Processor (SP) Firmware Update SP Firmware Using the TSM Service Application 12. From the Firmware Update dialog box, click Perform action. The update starts, and the Firmware Update Action Summary dialog box appears. Updating each service processor takes approximately ten minutes, and updating a master service processor takes approximately twenty minutes. 13.Monitor the status of the service processor firmware update in the Firmware Update Action Summary dialog box. a.
Updating Service Processor (SP) Firmware Update SP Firmware Using the TSM Service Application 16. Verify that the correct firmware version is loaded for each SP: a. If necessary, log on to the TSM Low-Level Link Application and perform a System Discovery. (Do not log off the TSM Service Application.) b. Display the Service Processor Actions dialog box, either by clicking SP Actions in the toolbar or by selecting Display>SP Actions. c.
Updating Service Processor (SP) Firmware Update SP Firmware Using the TSM Service Application If all SPs were updated successfully, you can skip to Section 8, Updating Processor Boot Code on page 8-1. Otherwise, continue with Determining If a Problem Has Occurred on page 7-14 to diagnose and correct problems you encountered. G06.
Updating Service Processor (SP) Firmware Determining If a Problem Has Occurred Determining If a Problem Has Occurred Note. Note that once the firmware update finishes and the SP is successfully reset, it can take up to 20 minutes before the Service Processor Firmware Version attribute is updated to display the new information. Follow all the verification steps included in the SP firmware update procedure. Otherwise, you might not know that the firmware update or reset did not finish successfully.
Updating Service Processor (SP) Firmware Other Indications of SP Firmware Update Problems If any of these problems occur, see Recovery for Problems Updating SP Firmware (Using TSM) on page 7-15.
Updating Service Processor (SP) Firmware Checking the State of the Service Connection Checking the State of the Service Connection 1. Using the TSM Service Application, open the Service Processor Actions dialog box, either by clicking SP Actions on the toolbar or by selecting Display>SP Actions. 2. From the Available Actions list, select SP Responsive Test. 3. Select the SP you want to test by clicking on it in the Service Processors (SPs) list. 4. Click Perform action. 5.
Updating Service Processor (SP) Firmware Updating Firmware Using the TSM Low-Level Link Application Updating Firmware Using the TSM Low-Level Link Application If you are unable to use the TSM Service Application, you can still update each SP by using the TSM Low-Level Link Application, if you have downloaded the firmware file spntcde9, as described under Download the SP Firmware File to the System Console on page 7-6.
Updating Service Processor (SP) Firmware Resetting an SP Using the TSM Low-Level Link 6. When the SP update finishes successfully, reset it, as described under Resetting an SP Using the TSM Low-Level Link on page 7-18. WARNING. To avoid hardware damage, never reset an SP if the firmware update does not finish successfully. See the TSM Low-Level Link Application online help for more information. Resetting an SP Using the TSM Low-Level Link To reset an SP, use the TSM Low-Level Link Application: 1.
Updating Service Processor (SP) Firmware Resetting an SP Using the TSM Low-Level Link 8. Verify that the correct version of SP firmware appears in the Service Processors (SPs) list. 9. Click Close. G06.
Updating Service Processor (SP) Firmware Updating SP Firmware Using the OSM Service Connection Updating SP Firmware Using the OSM Service Connection Use this procedure only if OSM is installed and configured. If TSM is installed and is your default, use the TSM Service Connection to update your SP firmware. Notes for Using OSM to Update SP Firmware • • • • The Multi-Resource Actions dialog box is used to update the SP firmware. After the SP firmware update is complete, you are asked to reset the SP.
Updating Service Processor (SP) Firmware Firmware Update for Fabric Side-Y (Using OSM) 3. Select Display>Multi-Resource Actions. The Multi-Resource Actions screen appears with unselected fields. VST938.vsd 4. From the Resource Type list, select SP. 5. From the Action list, select SP Firmware Update. 6. In the Filter by list, select the appropriate filter, Logical:Fabric Side-Y first. For example: VST939.vsd It might take a minute or so, for the SPs appear to appear in the SP Firmware list.
Updating Service Processor (SP) Firmware Firmware Update for Fabric Side-Y (Using OSM) VST949.vsd After the firmware update is complete with the SPs reset, the Compare State will display Up-rev and the firmware Version will display the new firmware file version. 7. Click Add All to add the SPs you want to update to the lower list. 8. Click Perform action. 9. Click OK when the SP-Confirm SP Firmware Update dialog box appears: The SP - Parameter Input dialog box appears. For example: VST906.vsd 10.
Updating Service Processor (SP) Firmware Firmware Update for Fabric Side-Y (Using OSM) vst945.vsd (Under Resource Name, the SP that has initially been updated displays a grey checkmark beside it. The other SP, awaiting update, displays a yellow question mark.) 11. To verify that firmware updates are in progress, select Action Summary. The Action Status Summary window appears with information about recent actions, including their status and their overall progress.
Updating Service Processor (SP) Firmware Firmware Update for Fabric Side-X (Using OSM) The Reset Progress bar keeps track of those SPs that pass the firmware reset. When all the selected SPs have completed the reset, the Passed column displays the number that are successfully reset. (A green checkmark replaces the grey checkmark by the SP under Resource Name in the SP Firmware resource list). Firmware Update for Fabric Side-X (Using OSM) Note.
Updating Service Processor (SP) Firmware Firmware Update for Fabric Side-X (Using OSM) 6. Enter the new file location the SP - Parameter Input dialog box. Use the $volume.subvolume.filename created during the most recent DSM/SCM Build/Apply and click OK. For example: $system.sys01.spcode9 After you click OK, the number of SPs that are currently being updated appear in the Running column under SP Firmware Update Progress. 7. To verify that firmware updates are in progress, select Action Summary.
Updating Service Processor (SP) Firmware Verifying the SP Firmware Update (Using OSM) Verifying the SP Firmware Update (Using OSM) 1. In the OSM Service Connection, double-click the group containing the PMF or IOMF CRU containing the SP whose status you want to verify. 2. Right click the SP. Select Attributes from the menu. 3. The Compare State should display Up-rev. You can also use the OSM Low Level Link Application to verify the firmware update: 1. Log on to the OSM Low-Level Link Application.
Updating Service Processor (SP) Firmware Verifying the SP Firmware Update (Using OSM) 8. Click Close. If all SPs were updated successfully, you can skip to Section 8, Updating Processor Boot Code on page 8-1. Otherwise, continue with Correcting a Failed SP Firmware Update (Using the OSM Service Connection) on page 7-28 to diagnose and correct problems you encountered. G06.
Updating Service Processor (SP) Firmware Correcting a Failed SP Firmware Update (Using the OSM Service Connection) Correcting a Failed SP Firmware Update (Using the OSM Service Connection) When an SP fails to update using the multiple firmware update, the number of failed SPs is displayed in the Failed column, and a red X appears by the SP that failed under Resource name in the SP Firmware resource list: 1. Select Action Summary. a.
Updating Service Processor (SP) Firmware Using OSM and Downloading the SP Firmware File to the System Console (Optional) 5. Under Download Path, click Browse to locate and select the \osm\bin directory. Under Options, verify that the Binary option is selected. Note. Verify that the Overwrite local files option is also selected. 6. Click OK. The Browse window closes, and an IXF - Receive dialog box appears, showing the download progress of the spntcde9 file. The download should take around 5 minutes. 7.
Updating Service Processor (SP) Firmware Updating Firmware Using the OSM Low-Level Link Application (Optional) Updating Firmware Using the OSM Low-Level Link Application (Optional) If you are unable to use the OSM Service Connection, you can still update each SP by using the OSM Low-Level Link, if you have downloaded the firmware file spntcde9, as described under Using OSM and Downloading the SP Firmware File to the System Console (Optional) on page 7-28.
8 Updating Processor Boot Code Processor boot code controls device boot and power-on diagnostic functions. This section describes the two common methods for updating the processor boot code and how to use either the OSM Service Connection or TSM Service Application to update the processor boot code for each PMF CRU in your system. See Table 8-1. Table 8-1.
Updating Processor Boot Code As documented in HS02865, there are at least three strategies for updating processor boot code firmware with subsequent methods for reloading the processors. See HS02865 for further details. This section combines the three Hotstuff strategies into two major methods: • Method 1: Using G06.24 OSM or TSM SPRs, Update Processor Boot Code Using the Online Option on page 8-4 With this method, it is assumed that you have at least the G06.
Updating Processor Boot Code Before You Begin Updating the Boot Millicode Before You Begin Updating the Boot Millicode Check Processor Status Before you update your firmware, verify that the system is up with at least one processor running a G06.00 or later version of the NonStop operating system: 1. If necessary, log on to the OSM or TSM Low-Level Link Application. 2. From the TSM or OSM toolbar, click Processor Status. Processor status should be Executing NonStop OS.
Updating Processor Boot Code Method 1: Using G06.24 OSM or TSM SPRs, Update Processor Boot Code Using the Online 2. Record the version of the processor boot code. 3. Repeat Steps 1 and 2 by using the SYSnn for your current RVU. For example: $SYSTEM SUPER 7> vproc $system.sys01.cpucode8 VPROC - T9617G03 - (30 MAR 1999) SYSTEM \WARRIOR Date 21 SEP 2000, 11:49:55 COPYRIGHT TANDEM COMPUTERS INCORPORATED 1986 - 1995 $SYSTEM.SYS01.
Updating Processor Boot Code Using TSM, Update Processor Boot Code Using the Online Option and G06.24 or Later TSM SPRs Using TSM, Update Processor Boot Code Using the Online Option and G06.24 or Later TSM SPRs Beginning with TSM 2001D (client and server versions) in G06.14, you can update the processor boot code for NonStop S-series servers (S70000, S7x000, S7600, S7800, S7400, S8x000) without taking the processor down for a hard reset action (or prime for reload action).
Updating Processor Boot Code Using TSM, Update Processor Boot Code Using the Online Option and G06.24 or Later TSM SPRs 6. Click Specify other to display the Specify Firmware File Location dialog box. Specify Firmware File Location Enter firmware file location and name: $volume.subvolume $system.sys02 File name CPUCODE9 VST654.vsd 7. Enter the volume and subvolume where the file to use as the source for the update resides. Use the $SYSTEM.SYSnn created during the most recent DSM/SCM Build/Apply. 8.
Updating Processor Boot Code Using OSM, Update Processor Boot Code Using the Online Option and G06.24 or Later OSM SPRs T7892G07^25AUG03^AAY^22Jul03^ VST728.vsd 10. From the Firmware Update dialog box, click Perform action. The update starts, and the Firmware Update Action Summary dialog box appears. 11. Monitor the status of the processor boot code update in the Firmware Update Action Summary dialog box. For example: VST964.
Updating Processor Boot Code Using OSM, Update Processor Boot Code Using the Online Option and G06.24 or Later OSM SPRs VST938.vsd 3. From the Resource Type list, select Processor. 4. From the Action list, select Online Boot Millicode Firmware Update. 5. From the Filter by list, select Logical: Fabric Side-Y. For example: 6. Click Add All to move the selected resources to update the lower list. 7. Click Perform Action. 8.
Updating Processor Boot Code Using OSM, Update Processor Boot Code Using the Online Option and G06.24 or Later OSM SPRs VST955vsd 10. To verify that firmware resets are in progress, select Action Summary. The Action Status Summary window appears with information about recent actions, including their status and overall progress. 11. Update the X-fabric for the processor boot code. From the Filter by list, select the appropriate filter, Logical:Fabric Side-X.
Updating Processor Boot Code Method 2: Using Your Current Pre-G06.24 OSM or TSM SPRs, Update the Processor Boot Code and Method 2: Using Your Current Pre-G06.24 OSM or TSM SPRs, Update the Processor Boot Code and Issue a Hard Reset or Equivalent Note. You can also perform a hard reset using the TSM or OSM Low-Level Link on all processors when you perform a system load instead of using the Reset action. See The Reset Operation on page 11-8.
Updating Processor Boot Code Using TSM, Update the Processor Boot Code and Issue a Hard Reset or Equivalent 5. Click Add all to move the resources to the Selected box. 6. Click Specify other to display the Specify Firmware File Location dialog box. 7. Enter the volume and subvolume where the file to use as the source for the update resides. Use the $SYSTEM.SYSnn created during the most recent DSM/SCM Build/Apply: G06.
Updating Processor Boot Code Using TSM, Update the Processor Boot Code and Issue a Hard Reset or Equivalent Specify Firmware File Location Enter firmware file location and name: $volume.subvolume $system.sys02 File name CPUCODE9 VST654.vsd 8. Click OK. 9. Click Yes when this message appears: You have specified a nonstandard firmware location. Compaq TSM will try to get the firmware information. It may take a few seconds.
Updating Processor Boot Code Using TSM, Update the Processor Boot Code and Issue a Hard Reset or Equivalent 11. Monitor the status of the processor boot code update in the Firmware Update Action Summary dialog box. For example: VST729.vsd When the action status appears as Completed, the processor boot code update is finished. 12. Repeat Steps 2 through 11 to update the Processor Boot Code, X-side.
Updating Processor Boot Code Using OSM, Update the Processor Boot Code and Issue a Hard Reset or Equivalent Using OSM, Update the Processor Boot Code and Issue a Hard Reset or Equivalent You can use OSM to update processor boot code, provided that you use the Hard Reset or Prime for Reload action option. This action can be done at the end of the procedure or when performing a system load. 1. Log on to the OSM Service Connection. 2. Select Display> Multi-Resource Actions.
Updating Processor Boot Code Using OSM, Update the Processor Boot Code and Issue a Hard Reset or Equivalent VST955vsd 10. To verify that firmware updates are in progress, select Action Summary. The Action Status Summary window appears with information about recent actions, including their status and overall progress. A successful update (partial screen) for the Y-fabric of the processor boot code: 11. Update the X-fabric for the processor boot code.
Updating Processor Boot Code Reset the Processors To Complete Updating the Processor Boot Code (Both for OSM and TSM) When you change the Filter by list from Y-side to X-side, this message appears: Changing a required filter results in your selections being cleared. Do you still wish to change the filter? 12. Click OK. 13. Click Add All to add the SPs you want to update to the Processor Boot Millicode Firmware lower list. 14. Click Perform Action. 15.
Updating Processor Boot Code Reset the Processors To Complete Updating the Processor Boot Code (Both for OSM and TSM) 3. Select the processor(s) that you want to halt. 4. From the Processor Actions list, select Halt. 5. Click Perform action. 6. Monitor status of the halt action. After the halt action has successfully finished, a completed message appears. 7. From the Processor Actions list, select Hard Reset and click Perform Action. For example: Caution.
Updating Processor Boot Code Reset the Processors To Complete Updating the Processor Boot Code (Both for OSM and TSM) G06.
9 Updating SCSI Boot Code (Pre-G06.08 RVU) This section describes how to check and, if necessary, update SCSI boot code for each PMF CRU in your system. Note. Update SCSI boot code only: • • If instructed to do so by DSM/SCM If you are not replacing the PMF CRUs in your system while migrating to the G06.24 RVU. Note. If you are migrating to the G06.24 RVU from an RVU prior to G06.08, you must update SCSI boot code after you perform the system load of the G06.
Updating SCSI Boot Code (Pre-G06.08 RVU) Using TSM to Update SCSI Boot Code (If Necessary) Using TSM to Update SCSI Boot Code (If Necessary) Before you update your firmware, verify that the system is up and running the G06.24 version of the NonStop Kernel operating system. This step is important if you are coming from a pre-G06.08 RVU. 1. If necessary, log on to the TSM Low-Level Link Application. 2. On the toolbar, click Processor Status. 3. The Processor Status should be Executing NonStop OS. 4.
Updating SCSI Boot Code (Pre-G06.08 RVU) Using TSM to Update SCSI Boot Code (If Necessary) vst900.vsd 4. Select all resources that have a current version different from the file version recorded in SCSI Boot Code Product Numbers on page 9-1, and then click Add to move selected resources to the Selected box. If all firmware versions match, you do not need to perform the update for the selected fabric (X or Y). If you have not yet checked the firmware in the other fabric, repeat Steps 2 through 6.
Updating SCSI Boot Code (Pre-G06.08 RVU) Using OSM to Update SCSI Boot Code (If Necessary) Using OSM to Update SCSI Boot Code (If Necessary) Note. OSM can only be installed on G06.08 RVUs or later; thus the IBOOT (T0503) file should already be installed. Instructions are provided in case a new firmware file is introduced after the most current RVU is initially released. 1. Before you update your firmware, verify that the system is up and running the G06.
10 Running ZPHIRNM 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. This section 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.
Running ZPHIRNM Back Up (Copy) Files in the $SYSTEM.ZTCPIP Subvolume Back Up (Copy) Files in the $SYSTEM.ZTCPIP Subvolume If you are upgrading to the G06.24 RVU, you must make backup copies of these files in the $SYSTEM.ZTCPIP subvolume before running ZPHIRNM, which overwrites them with sample versions.
Running ZPHIRNM Stop All Applications Stop All 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. Stop all other applications, except for TMF and the OSS file system.
Running ZPHIRNM Back Up the Spooler Control Files See Support Note S99086, NSK Spooler—Migration and Draining Instructions, for more information. You can also review Section 1 and Appendix H in the Spooler Utilities Reference Manual. Back Up the Spooler Control Files While the spooler environment is closed, back up the spooler control files. Backing up the spooler will render a known database from which you recover in case of a catastrophic spooler failure.
Running ZPHIRNM Steps for Running ZPHIRNM 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 DSM/SCM User’s Guide. Steps for Running ZPHIRNM 1. At a TACL prompt, enter this command from the DSM/SCM subvolume: > RUN ZPHIRNM $vol.
Running ZPHIRNM Steps for Running ZPHIRNM For managing OSS files, you might see a display similar to: OSS: Directories: Directories in new configuration .................. Directories in old configuration .................. 110 110 Directories in new configuration only ............. Directories in old configuration only ............. Directories shared by new and old configurations .. 0 0 110 Directories processed in new config ............... Directories processed in old config (obsolete) ....
Running ZPHIRNM Steps for Running ZPHIRNM 4. Run the OSS merge_whatis command. (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 either one or both of the following, depending on your OSS environment: /bin/merge_whatis /bin/merge_whatis /nonnative/usr/share/man The CISC version of the c89(1) man page resides in the /nonnative directory. Note.
Running ZPHIRNM Verify That ZPHIRNM Ran Successfully 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. A nonfatal error is one that affects processing only for a single subvolume.
11 Loading the G06.24 RVU This section describes how to load the G06.24 version of the NonStop Kernel operating system into the memory of each processor in a NonStop S-series server. Unless OSM is installed and configured, TSM is used to load the system processors. Alerts Before performing a system load: • Before halting the processors, stop any applications that are still running, including TMF. Note.
Loading the G06.24 RVU Halt the Processors Halt the Processors 1. If necessary, log on to the TSM Low-Level Link Application or the OSM Low-Level Link. The following steps are similar whether you are using the TSM or 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. For example: VST800.vsd 5. Click Perform action. 6.
Loading the G06.24 RVU Replace Processor or Other System CRUs 7. When the Action Status box confirms that all processors have halted, close the Processor Status dialog box. For example: VST830.vsd 8. Close the OSM Service Connection or TSM Service Application window and any OutsideView windows, but do not log off of the OSM or TSM Low-Level Link Application; you will use it to perform a system load in the next procedure. Replace Processor or Other System CRUs Note.
Loading the G06.24 RVU System Load Using the TSM or OSM Low-Level Link System Load Using the TSM or OSM Low-Level Link The operating system is loaded from disk into the memory of one processor. (This operation is sometimes also called a device load or cold load.) All possible paths to processor 0 are tried. If these fail, all possible paths to processor 1 are tried. The remaining processors are loaded by commands in the CIIN file. The initial TACL process stops after executing the CIIN file. 1.
Loading the G06.24 RVU System Load Using the TSM or OSM Low-Level Link 7. Monitor the System Status (which contains initial high-level messages) and Detailed Status (which contains low-level messages) boxes. For example, as shown in TSM: VST810.vsd Messages indicate the progress and completion of the system load and the reload of any processors configured in the CIIN file to start.
Loading the G06.24 RVU Reload the Remaining Processors (If Necessary) Reload the Remaining Processors (If Necessary) After the first processor is loaded, the initial TACL process automatically invokes the CIIN file unless the CIIN file is disabled. The CIIN file contains commands that establish the permanent TACL process pair for the system console. The CIIN file might also contain commands to reload all processors.
Loading the G06.24 RVU Check the Status of the Processors CPU 1: reloaded. CPU 2: reloaded. CPU 3: reloaded. Check the Status of the Processors 1. Check the status of the processors to verify that they are all executing the NonStop Kernel. 2. From the OSM Low-Level Link or the TSM Low-Level Link window toolbar, click Processor Status to display the Processor Status dialog box. 3. When all processors are executing the NonStop Kernel, continue with the upgrade procedure.
Loading the G06.24 RVU The Reset Operation Because the primary system disk is powered off, the system load is forced to use the mirror disk half (normally, the disk with the latest disk label timestamp is used, and the other disk half is placed in a STOPPED state). The system load uses the mirror disk regardless of its state when the system was stopped. Note.
12 Resuming Normal Operations Several tasks must be performed after system load before you can resume normal system operations, as described in this section. • • • • • • • Update TCP/IP Configuration Files Check Processor Status (Using TSM or OSM) Perform Other Firmware Updates Configure the Spooler Start User and System Applications Reset and Start the Mirror System Disk (If Necessary) Configure Specific Products (Post-System Load) Update TCP/IP Configuration Files Note.
Resuming Normal Operations Step 2: Check the PROTOCOL File Perform a FUP DUP operation to rename the sample configuration files from the G06.24 SUT to the real file name. Note. Only copy these configuration files 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.
Resuming Normal Operations ipv6 icmpv6 41 58 Step 3: Ensure That PORTCONF and SERVICES Files Are Complete IP ICMP internet protocol for v6 internet control message protocol for v6 Step 3: 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.
Resuming Normal Operations Reconfigure System Console Applications Reconfigure System Console Applications Note. You can have both the TSM client and the OSM client-based components on your system consoles. However, to avoid duplicate dial-outs, use either the OSM Notification Director (ND) or TSM Notification Director, but not both.
Resuming Normal Operations Perform Other Firmware Updates Perform Other Firmware Updates Update SWAN and SWAN 2 CLIP Firmware If you have a ServerNet wide area network (SWAN) concentrator connected to your NonStop S-series server, follow the instructions in Appendix C, Updating SWAN Concentrator CLIP Firmware, to update the CLIP firmware after doing a system load of the G06.24 RVU.
Resuming Normal Operations • Update ServerNet/FX and ServerNet/FX2 Firmware (Overview) Fibre Channel ServerNet adapter (FCSA) Note that the ServerNet/FX and ServerNet/FX 2 adapters do not have the autofirmup feature. Use either the TSM Service Application, or if installed, the OSM Service Connection. Only an HP service provider is authorized to install and configure an FCSA and G4SA.
Resuming Normal Operations Update ServerNet/FX and ServerNet/FX2 Firmware (Overview) To Set a Cluster Number (Using TSM) 1. In the TSM Management window, select the FXSA FRU. 2. Select Display> Actions to display the TSM Actions dialog box. 3. Select Set FOX Cluster Number and then click Perform Action. 4. Select an integer number from 1 through 14 for a new cluster number, making sure that it is different from the current cluster number. 5.
Resuming Normal Operations Update ServerNet/FX and ServerNet/FX2 Firmware (Overview) VST450.vsd 6. After moving all FXSA or FX2SA FRUs to be stopped to the lower resource list, click Perform Action. Note. The associated LBU is also stopped. 7. When the FRUs are in the Stopped state, select Firmware Update from the Action list and click Perform Action to update the firmware for any FRUs listed in the lower resource list. G06.
Resuming Normal Operations Configure the Spooler Confirmation dialog boxes prompt you to enter an (optional) alternative to the default file location. The Progress bar at the bottom of the Multi-Resource Actions dialog box tracks the success or failure of each action. (Click Action Summary to get details on failed actions). 8. Upon successful completion of the firmware updates, select Start from the Action list to start selected FRUs (and their associated LBUs). 9.
Resuming Normal Operations Start User and System Applications Start User and System Applications You can now start your application software. Follow your site’s procedures for executing the system configuration and startup (command) files to accomplish this. DSM/SCM is often started automatically by a system command file. If not, you must start it manually as described next. Before Starting DSM/SCM Initialize SQL 1. Check that TMF is started: > TMFCOM STATUS TMF 2.
Resuming Normal Operations Start DSM/SCM 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 - T6031D46 - (31MAR2003) Copyright Hewlett Packard Development Company L.P. 1993-2003 NOTICE: * * * * If the hometerm chosen during INITENV, $zhome, is not currently in a paused state, STARTSCM and DSM/SCM server processes may hang indefinitely.
Resuming Normal Operations Configure Specific Products (Post-System Load) For example: > scf SCF - T9082G02 - (14JAN02) (03JAN02) - 04/28/2003 10:54:23 System \TEENY Copyright Compaq Computer Corporation 1986 - 2002 (Invoking \TEENY.$SYSTEM.STARTUP.SCFCSTM) 1-> reset disk $system 2-> start disk $system STORAGE W01001 To START the disk, SCF must revive the information on \TEENY.$SYSTEM. This operation might IMPACT system performance, especially users of $SYSTEM.
Resuming Normal Operations Configure OSS In summary, the latest Expand T9057 SPRs remove the use of Super Timefactors in Expand routing. The original time factor method of routing used before T9057G06^AEM (G06.08 RVU) is now used starting with SPR T9057AFL and G06.20. SPEEDK is now mapped to a time factor, and values of SPEEDK for FOX networks or faster are mapped to a time factor of 1. As a result, review settings for SPEEDK, SPEED, and RSIZE to verify that the proper routing is maintained.
Resuming Normal Operations Configure SMF (Optional) The inetd process should be run 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. See the inetd(8) reference page in the Open System Services Shell and Utilities Reference Manual for more information.
Resuming Normal Operations Configure the Remote Duplicate Database Facility (RDF) 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. If remote access to files supported by SMF is needed, the remote system must be running one of these RVUs: • • • Any G-series RVU D43.02 or later D4n.nn D-series RVUs D35.
Resuming Normal Operations Upgrade the TNOS Server and TNOS Utility (Optional) Upgrade the TNOS Server and TNOS Utility (Optional) A miscoded TNS (non-native) program can erroneously generate operand addresses that are not adequately aligned for the TNS instruction set architecture. The program can then get unpredictable results when referencing those memory operands, on both TNS and TNS/R systems, whether accelerated or not.
Part II. Fallback Tasks Part II describes the tasks for falling back from the G06.24 RVU to a G06.06 or later RVU. If you encounter a problem that cannot be resolved while running G06.24, you can fall back to your previous G-series RVU, provided you have already installed the appropriate fallback SPRs for your system. These sections describe the tasks for falling back to your previous RVU from G06.
Part II. Fallback Tasks G06.
13 Preparing to Fall Back If you encounter a problem that cannot be resolved while running the G06.24 RVU, you can fall back to a G06.06 or later G-series RVU, provided that you have already installed the appropriate fallback SPRs, as described in Section 3, Installing SPRs Before Upgrading to the G06.24 RVU. If you did not install the appropriate fallback SPRs before installing the G06.24 RVU, contact your service provider. Alerts Before falling back from the G06.24 RVU: • • • Review G06.
Preparing to Fall Back • • Summary of Fallback Tasks Starting with the G06.23 RVU, there are fallback considerations regarding NonStop SQL/MX Release 2.0. See NonStop SQL/MX Release 2.0 (G06.23 and G06.24) on page 1-28. For SQL/MX Release 2.0: Before falling back, to minimize the risks involved with falling back without a clean TMF shutdown, use the appropriate SQL (MX or special MP) GOAWAY utility to delete all native-format SQL/MX objects and their resource forks.
Preparing to Fall Back DP2 DP2 If you have set the AUDITTRAILBUFFER or the SQLMXBUFFER attribute to 128 or more, you need to reset the value to 0 before falling back to G06.16 or earlier RVU. If you fail to do so, TMF might not start, or a disk volume could go offline. You can recover from this situation after the fallback by using the SCF ALTER command. See the Interactive Upgrade Guide for details.
Preparing to Fall Back Spooler Spooler If you have to fall back to an RVU prior to G06.00 and the spooler control file format is from a spooler version prior to T9101ADM, you must restore copies of both the control file and the collection files that were in use. If your previous product version of spooler was T9101D41 SPR ADM or later, you do not need to restore copies of both the control file and the collector data files if you back out of your G06.24 RVU.
Preparing to Fall Back SQL/MX 2.0 SQL/MX 2.0 Metadata tables created and used by SQL/MX Release 2.0 running on or after G06.23 are different than those metadata tables used on prior SQL/MX releases, and the tables are very different than those used by SQL/MP. You must be on at least Release 1.8 to migrate or to fall back. Migration and fallback considerations do apply. See TMF (G06.23 and G06.24) on page 1-38 and DP2.
Preparing to Fall Back WAN Manager (T8365) G06.
14 Backing Out the DSM/SCM Revision This section describes how to submit a DSM/SCM backout request to return from G06.24 to your previous RVU. If you selected DSM/SCM to manage OSS files and you need to fall back to a pre-D46 DSM/SCM PVU, you must run the DSM/SCM FALLBACK macro from the ZDSMSCM subvolume. The FALLBACK macro can be exported from any D46 PVU in the DSM/SCM archive, and then placed in the ZDSMSCM subvolume. Before Backing Out the Revision 1.
Backing Out the DSM/SCM Revision Start the Target Interface (ZPHITI) Start the Target Interface (ZPHITI) 1.
Backing Out the DSM/SCM Revision Submit a Backout Request Submit a Backout Request 1. From the ZPHITI Main Menu, enter 3 (Perform target activities) in the Selection number field, and press F1.
Backing Out the DSM/SCM Revision Submit a Backout Request 3. In the Selection number field, enter 2 (Perform backout to S/W), and press F1.
Backing Out the DSM/SCM Revision Submit a Backout Request DSM Software Configuration Manager Backout - Processing Backout ============================================================================== \ELI Prior snapshot 2002-04-14:18:03:03 DEFAULT Last S/W applied on SYS00 on 2000-04-14:18:01 Backout 2000-04-18:10:59:34 ============================================================================== Request is being processed. Status information will appear below indicating progress.
Backing Out the DSM/SCM Revision Submit a Backout Request A complete set of operator instructions might look like this: DSM Software Configuration Manager Backout - Complete Backout ============================================================================== \ELI Prior snapshot 2002-04-14:18:03:03 DEFAULT Last S/W applied on SYS on 2000-04-14:18:01 Print operator instructions on: ============================================================================== Placement of files for this Backout is complet
Backing Out the DSM/SCM Revision Monitor the Backout Process Monitor the Backout Process 1. Log on to DSM/SCM (Start>Programs>Dsm_scm>DSMSCM). 2. Select 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: vst100.vsd G06.
Backing Out the DSM/SCM Revision Monitor the Backout Process G06.
15 Returning Firmware to Previous Versions This section describes how to return processor boot code, SP firmware, and SCSI boot code back to the earlier product versions before loading the previous operating system image. Alerts Processor Boot Code If you are returning to an RVU prior to the G06.16 RVU, you must return processor boot code back to the earlier PVU before performing a system load of your previous RVU. If you are returning to a G06.
Returning Firmware to Previous Versions Return the Processor Boot Code to the Previous Version For example: $SYSTEM SUPER 8> vproc $system.sys01.cpucode9 VPROC - T9617G03 - (30 MAR 1999) SYSTEM \ELI Date 21 MAR 2000, 11:30:35 COPYRIGHT TANDEM COMPUTERS INCORPORATED 1986 - 1995 $SYSTEM.SYS01.CPUCODE9 Binder timestamp: Version procedure: 25AUG1999 13:42:26 T7892G05^03SEP99^25Aug99^ where SYS01 is the previous operating system image subvolume.
Returning Firmware to Previous Versions Download the Previous SP Firmware File to the System Console Use this information to verify that the update to the previous version was successful. Download the Previous SP Firmware File to the System Console Download the previous SP firmware file into the spcode9 directory on the hard drive of your system console in the event you encounter problems when updating the SP firmware.
Returning Firmware to Previous Versions Return the SCSI Boot Code to the Previous Version (Using TSM) To check the new version of SCSI boot code, enter: >VPROC $SYSTEM.SYSnn.IBOOT Use this information from the VPROCs to verify that the update to the previous version was successful. Return the SCSI Boot Code to the Previous Version (Using TSM) From the TSM Service Application, use the Firmware Update dialog box to update the SCSI boot code for each PMF customer-replaceable unit (CRU) in your system. 1.
Returning Firmware to Previous Versions Returning SP Firmware to the Previous Version (Using OSM) Returning SP Firmware to the Previous Version (Using OSM) 1. Select Display>Multi-Resource Actions. The Multi-Resource Actions dialog box appears with unselected fields. 2. From the Resource Type list, select SP. 3. From the Action list, select SP Firmware Update. 4. From the Filter by list, select the appropriate filter, Logical:Fabric Side-Y first. 5.
Returning Firmware to Previous Versions Returning Bootcode Firmware to the Previous Version (Using OSM) 15. Check that all SPs have completed successfully. Returning Bootcode Firmware to the Previous Version (Using OSM) 1. Log on to the OSM Service Connection. 2. Select Display> Multi-Resource Actions. The Multi-Resource Actions dialog box appears with unselected fields. 3. From the Resource Type list, select SP. 4. From the Action list, select Processor Boot Millicode Firmware Update. 5.
Returning Firmware to Previous Versions Returning Bootcode Firmware to the Previous Version (Using OSM) When you change the filter from Y-side to X-side, this message appears: Changing a required filter results in your selections being cleared. Do you still wish to change the filter? 12. Click OK. 13. Click Add All to add the SPs you want to update to the lower list. 14. Click Perform Action. 15. Click OK when the Confirm Processor Boot Millicode Firmware Update dialog box appears.
Returning Firmware to Previous Versions Returning Bootcode Firmware to the Previous Version (Using OSM) G06.
16 Running ZPHIRNM to Reactivate the Previous Software Revision This section describes how to run the ZPHIRNM program again to change the temporary names of the previous product files back to their actual names. Alerts Before running ZPHIRNM: • • • • Applications that use files that are being replaced should not be running. To avoid any possibility of conflict, stop all applications, except for the TMF subsystem, before running ZPHIRNM. You must have rename (purge) access to all files being renamed.
Running ZPHIRNM to Reactivate the Previous Software Revision Run ZPHIRNM 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 Section 1 in the Spooler Utilities Reference Manual.
Running ZPHIRNM to Reactivate the Previous Software Revision Verify That ZPHIRNM Ran Successfully Verify That ZPHIRNM Ran Successfully 1. Review the log file. 2. 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.
Running ZPHIRNM to Reactivate the Previous Software Revision Verify That ZPHIRNM Ran Successfully G06.
17 Loading the Previous RVU and Resuming Normal Operations This section describes how to load the previous RVU back into the memory of each processor in the server and resume normal operations. Alerts Before performing a system load, note: • • • • • • If you are returning to an RVU prior to the G06.
Loading the Previous RVU and Resuming Normal Operations Prepare to Stop the System Prepare to Stop the System Before halting the processors: 1. Stop all user applications. 2. Stop TMF and DSM/SCM. For example: 5> TMFCOM STOP TMF 6> VOLUME $dsmscm_vol.ZDSMSCM 7> RUN STOPSCM Halt the Processors Halt all processors from the TSM Low-Level Link Application or from the OSM Low-Level Link. Remove Hardware Installed During Migration If you installed or replaced hardware during your migration to the G06.
Loading the Previous RVU and Resuming Normal Operations Perform a System Load With the Previous SYSnn and CONFxxyy Perform a System Load With the Previous SYSnn and CONFxxyy Perform a system load, except in Step 3, enter the SYSnn of your previous operating system image subvolume, and in Step 4, select the Saved version of the CONFxxyy configuration file that you created under Save the Current Configuration File (CONFxxyy) on page 4-1. Caution. Starting with the G06.
Loading the Previous RVU and Resuming Normal Operations Resume Normal Operations Resume Normal Operations Resume normal operations by invoking the proper startup files to start system processes and user applications after falling back to the previous RVU. Note. If you receive this error message when you attempt to start DSM/SCM: ERROR: *1081* PATHCTL FILE IS INCOMPATIBLE 1. Stop the $YPHI PATHMON process: > VOLUME $dsmscm_vol.ZDSMSCM > STOP $YPHI 2.
Loading the Previous RVU and Resuming Normal Operations Configure Spooler Configure Spooler RVUs for G06.00 and later RVUs contain spooler product version T9101D46, which introduced a spooler control file in a new format. Although it is still a type 128 file, internally it is considerably different from the format used in the base T9101D41 spooler.
Loading the Previous RVU and Resuming Normal Operations G06.
A Using DSM/SCM to Install SPRs SPRs provide new features between RVUs or correct software problems from a previous RVU. This appendix describes tools available for investigating SPRs and instructions on how to install SPRs. Caution. Do not apply any SPR to an RVU without first verifying (using Scout for NonStop Servers, for example) that the SPR can be installed on that specific G-series RVU. See the G06.
Using DSM/SCM to Install SPRs DSM/SCM DSM/SCM DSM/SCM has automatic features that can help you keep records of SPRs. You can use the DSM/SCM Planner Interface to generate a number of 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.
Using DSM/SCM to Install SPRs Determine the Current SYSnn 3. Save the current configuration by using a unique file name. At the SCF prompt, enter: -> SAVE CONFIGURATION xx.yy where xx.yy variable is a number from 0.0 through 99.99. This example saves the current system configuration to the file $SYSTEM.ZSYSCONF.CONF1101: -> SAVE CONFIGURATION 11.1 The configuration file $SYSTEM.ZSYSCONF.CONF1101 has been created.
Using DSM/SCM to Install SPRs Receive the SPR Into the DSM/SCM Archive 3. 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 000 255,255 $SYSTEM.SYS01.OSIMAGE $YMIOP.#CLCI Swap File Name: $SYSTEM.#0 Note. DSM/SCM notifies you in the Build/Apply Request dialog box if a SYSGEN is required and then runs SYSGEN automatically.
Using DSM/SCM to Install SPRs Create a New Software Configuration That Includes the SPR 8. In the Receive Software Request dialog box, click Scheduling. 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 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.
Using DSM/SCM to Install SPRs Print Operator Instructions From the Target Interface (ZPHITI) 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, type: RUN ZPHITI The TI Logon screen appears. 3. Type your user ID and password and press F1 to log on to the Target Interface. The Main Menu appears. 4.
Using DSM/SCM to Install SPRs • • If Running INSTALL^TEMPLATES Is Required $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, type Y and press Enter. 3. When prompted, type a file name for the log file and press Enter.
Using DSM/SCM to Install SPRs If Running INSTALL^TEMPLATES Is Required 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.
Using DSM/SCM to Install SPRs If a System Load Is Required 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. The following 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, 1985-2000 SECURE ($SYSTEM.
Using DSM/SCM to Install SPRs Perform a System Load Perform a System Load When you perform a system load, the operating system is loaded from disk into the memory of one processor. (This operation is sometimes called a device load or cold load.) All possible paths to processor 0 are tried; if these fail, all possible paths to processor 1 are tried. The remaining processors are loaded by commands in the CIIN file. The initial TACL process stops after executing the CIIN file. 1.
Using DSM/SCM to Install SPRs Reload the Processors (If Necessary) The other processors are now primed for reload. 4. On the toolbar of the OSM Low-Level Link or TSM Low-Level Link Application window, select Processor Status. The Processor Status dialog box should show Executing NonStop OS. EMS event stream and startup TACL windows are automatically launched on the system console. The process might take a few seconds. Note.
Using DSM/SCM to Install SPRs Start Your Applications and Processes G06.
B Installing the Latest DSM/SCM SPRs and Client Software Before You Begin Installing DSM/SCM and Client SPRs Note. • • • If you want DSM/SCM to manage OSS files, you must install both the D46 DSM/SCM SPR and the client version before you receive the SUT. You can install the D46 client version (T6031D46^ABJ) either before or after installing the D46 T6031^ABJ SPR. However, this appendix describes installing the D46 SPR first on the server side and then on the client side.
Installing the Latest DSM/SCM SPRs and Client Software Before You Begin Installing DSM/SCM and Client SPRs Table B-1. G-Series DSM/SCM PVUs and SPRs (continued) PVU SPR RVU Description (Major changes)* T6031D46 ABE G06.19 Provides an updated version of the DSM/SCM CNFGINFO tool. OSS developers can use this tool to create A7CINFO files in their products' DSVs. A7CINFO files are required by DSM/SCM for automated OSS file management. T6031D46 ABF G06.
Installing the Latest DSM/SCM SPRs and Client Software Before You Begin Installing the Software Identification (SWID) SPR Before You Begin Installing the Software Identification (SWID) SPR If you are upgrading from a pre-G06.20 RVU, besides restoring T6030D31 and T6031D46, you must also upgrade the Software Identification (SWID) (T9298D40AAK) product at the same time to avoid a problem with ZPHIRNM renaming hybrid SRLs to fabricated names.
Installing the Latest DSM/SCM SPRs and Client Software Determine the Product Version of DSM/SCM on the Host System Determine the Product Version of DSM/SCM on the Host System 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.
Installing the Latest DSM/SCM SPRs and Client Software Determine the Product Version of DSM/SCM on the Client VST004.vsd To install the DSM/SCM client, see Install the DSM/SCM Client From ZDSMSCM on page B-18. G06.
Installing the Latest DSM/SCM SPRs and Client Software Copy (RESTORE) the D46 DSM/SCM Product Version and SWID (Optional) to Disk Copy (RESTORE) the D46 DSM/SCM Product Version and SWID (Optional) to Disk To copy the D46 product version of DSM/SCM and the SWID product (optional, depending on your current RVU) from the G06.24 RVU to disk, at a TACL prompt, enter the RESTORE command: >RESTORE/OUT $S.#nnn.DSM/$tape, ($*.R6030D31.*,$*.R6031D46.*,$*.R9298D40.
Installing the Latest DSM/SCM SPRs and Client Software Request name: SOFTWARE Receive the D46 SPRs for DSM/SCM 2003-12-07-19:09:39 Request description: SOFTWARE 2003-12-07-19:09:39 D46 DSM and SWID VST353.vsd 5. Under Options, click Input source. DSM/SCM displays the Request Source Options dialog box. 6. Select Volume.subvolume. 7. In the Add text box, enter each distribution subvolume for the DSM/SCM files that you specified earlier in the RESTORE command: $DSMSCM.R6030D31 $DSMSCM.R6031D46 $DSMSCM.
Installing the Latest DSM/SCM SPRs and Client Software Receive the D46 SPRs for DSM/SCM 3 $DSMSCM.R6031D46 $DSMSCM.R6030D31 $DSMSCM.R6031D46 $DSMSCM.R9298D40 VST350.vsd 8. Click OK. You are returned to the Receive Software Request dialog box. 9. Click OK to run the request immediately. (The request takes approximately 15 minutes to finish.) G06.
Installing the Latest DSM/SCM SPRs and Client Software Receive the D46 SPRs for DSM/SCM 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: SOFTWARE 2002-12-07-19:09:39 Input software Complete VST351.vsd 10. Select Window>Refresh to update the Software in Archive dialog box to include the received software. G06.
Installing the Latest DSM/SCM SPRs and Client Software Create a New Software Revision for DSM/SCM D46 SPR and SWID Create a New Software Revision for DSM/SCM D46 SPR and SWID 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.
Installing the Latest DSM/SCM SPRs and Client Software Build and Apply the DSM/SCM D46 Software Revision b. Enter a description of the changes to the existing text. For example, if you are migrating from a pre-G06.20 RVU, you might enter: Added 05/07/2004: G06.24DSM/SWID c. Click OK to add a written history of revisions to existing notes. Build and Apply the DSM/SCM D46 Software Revision The Build process creates an activation package of products contained in the new software revision.
Installing the Latest DSM/SCM SPRs and Client Software Build and Apply the DSM/SCM D46 Software Revision c. Click OK. VST254.vsd 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.
Installing the Latest DSM/SCM SPRs and Client Software Rename the Applied DSM/SCM D46 Files Rename the Applied DSM/SCM D46 Files 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.
Installing the Latest DSM/SCM SPRs and Client Software If Running INSTALL^TEMPLATES Is Required 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.
Installing the Latest DSM/SCM SPRs and Client Software Restart Applications 1. Rename the current files: -> rename newres, oldres -> rename newnres, oldnres 2. Run the INSTALL^TEMPLATES macro again and use the file names newres and newnres. The following message indicates that the templates are successfully installed: >$SYSTEM.SYS00.FUP /NAME $Z03M,INV :INBUF.1,OUTV :OUTBUF.
Installing the Latest DSM/SCM SPRs and Client Software Verify That the D46 Product Version of DSM/SCM Is Installed These messages appear: 8> startscm DSM/SCM Process Startup Function - STARTSCM - T6031D46 - (31MAR2003) Copyright Hewlett Packard Development Company L.P. 1993-2003 NOTICE:* If the hometerm chosen during INITENV, $zhome, * is not currently in a paused state, STARTSCM and DSM/SCM * server processes may hang indefinitely.
Installing the Latest DSM/SCM SPRs and Client Software Verify That SWID Is Installed \FOXII $GREECE.T6031ABJ 8> vproc cbexe VPROC - T9617D42 - (20 DEC 2000) SYSTEM \FOXII Date 24 JAN 2004, 04:47:11 COPYRIGHT TANDEM COMPUTERS INCORPORATED 1986 - 2000 $GREECE.T6031ABJ.CBEXE Binder timestamp: Version procedure: Version procedure: Target CPU: \FOXII $GREECE.T6031ABJ 16JAN2004 04:10:20 S7032D20^27FEB04^SWARCCP^AAH T6031D46_13JAN2004_16JAN2004ABJ UNSPECIFIED 9> \FOXII $GREECE.
Installing the Latest DSM/SCM SPRs and Client Software Recovery for Problems While Installing the D46 Version of DSM/SCM Recovery for Problems While Installing the D46 Version of DSM/SCM If you encounter problems while installing the D46 version of DSM/SCM, see the following information and the DSM/SCM User’s Guide.
Installing the Latest DSM/SCM SPRs and Client Software Alert (DSM/SCM T6031D46^ABJ Client) Alert (DSM/SCM T6031D46^ABJ Client) Do not attempt to use DSM/SCM T6031D46^ABJ client software until you have first installed T6030/T6031D30^AAO or later software product revisions (SPRs) or the T6031D46 PVU on your host system. See Table 3-1, DSM/SCM Client and Server Compatibility, on page 3-5. Limited DSM/SCM operation is available if you run T6031D46^ABJ client software with pre-AAO server software.
Installing the Latest DSM/SCM SPRs and Client Software Copy the ZDSMSCM Client File From the Host 5. Make a note of the IP address and port number. 6. Close the dsmscm.ini file. Copy the ZDSMSCM Client File From the Host Note. If you are not using OutSideView on the PC that manages DSM/SCM: 1. On the NonStop Kernel host system, make $volume.ZDSMSCM the current subvolume. 2.
Installing the Latest DSM/SCM SPRs and Client Software Install the DSM/SCM Client Software Install the DSM/SCM Client Software 1. Using Windows Explorer, double-click Setup.exe. A DSM/SCM Setup screen appears, and an Enter Object Manager Server Class dialog box appears with the default OM-001. VST010.vsd 2. Click Next to accept the default. The Enter Software Product Group Type (shared or private) dialog box appears. VST021.vsd G06.
Installing the Latest DSM/SCM SPRs and Client Software Install the DSM/SCM Client Software 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. 4. The Enter CNFGINFO Process Name dialog box appears with the default name $ZPHC. VST015.vsd 5.
Installing the Latest DSM/SCM SPRs and Client Software Install the DSM/SCM Client Software The Choose Destination Location dialog box appears with the default path displayed, based on your operating system (either Windows 2000 or Windows XP Professional): VST025.vsd 7. Click Next to accept the default. You are now prompted to enter an IP address. VST030.vsd 8.
Installing the Latest DSM/SCM SPRs and Client Software Install the DSM/SCM Client Software You are now prompted to enter an IP port number. VST035.vsd 9. Type the IP port number for the Winsock service (see Determine the Current IP Address and Port Number on page B-19), 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.
Installing the Latest DSM/SCM SPRs and Client Software Create an Emergency Repair Disk (ERD) You are asked if you would like to run DSM/SCM. VST045.vsd 11. Click No and go to Create an Emergency Repair Disk (ERD) on page B-25. 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: VST130.
Installing the Latest DSM/SCM SPRs and Client Software Create an Emergency Repair Disk (ERD) 3. If you are running Windows 2000: a. The Backup utility appears. Click Emergency Repair Disk. b. You are prompted to insert a disk into drive A. c. Label a disk Emergency Repair Disk and insert it into drive A. Click OK. d. The Emergency Repair Disk utility copies repair information to the disk. When this process finishes, you are informed that the repair information was saved successfully. e.
C Updating SWAN Concentrator CLIP Firmware If necessary, you can update the SWAN or SWAN 2 concentrator CLIP firmware after you have completed a system load of the new RVU. You can use either the OSM Service Connection or TSM, depending on which one you have installed. TSM provides a guided procedure for updating firmware for both SWAN and SWAN 2. OSM provides a Multi-Resource Actions dialog box.
Updating SWAN Concentrator CLIP Firmware Using the SWAN Fast Firmware Update Guided Procedure (Recommended if Using TSM) Yellow caution symbols might appear on enclosure icons and on SWANs during the firmware update. These caution symbols should disappear after you have completed the SWAN update. Using the SWAN Fast Firmware Update Guided Procedure (Recommended if Using TSM) Follow the instructions in the guided procedure.
Updating SWAN Concentrator CLIP Firmware Using the SWAN Fast Firmware Update Guided Procedure (Recommended if Using TSM) vst832.vsd 3. Select Updating CLIP firmware. 4. Click Start. The Select CLIP Collection dialog box appears. For example: G06.
Updating SWAN Concentrator CLIP Firmware Using the SWAN Fast Firmware Update Guided Procedure (Recommended if Using TSM) vst864.vsd 5. In the Select CLIP Collection dialog box, select the CLIPs to be updated: a. From the Adapter Type list, select either SWAN or SWAN2. b. Select _All_CLIP_2s_if adapter is SWAN2 or _All_CLIP_s if adapter is SWAN. c. From the CLIP List in Selected Collection, select the required CLIPs and click Add CLIPs. d. Click Use. The Select Action dialog box appears. 6.
Updating SWAN Concentrator CLIP Firmware Using the SWAN Fast Firmware Update Guided Procedure (Recommended if Using TSM) vst835.vsd 8. If you want to start the CLIPs after firmware, select Start CLIPs after Update? Otherwise, click Start after the SWAN CLIP firmware update is complete. 9. Click Update Firmware. TSM stops the SERVER objects and initiates a firmup of the CLIPs. The Firmware Update Progress Dialog box appears. 10.
Updating SWAN Concentrator CLIP Firmware Using the SWAN Fast Firmware Update Guided Procedure (Recommended if Using TSM) 11. When you have finished updating firmware, select OK. If you have problems with the Fast Firmware Update, see If the SWAN Fast Firmware Update Fails on page C-7. G06.
Updating SWAN Concentrator CLIP Firmware If the SWAN Fast Firmware Update Fails If the SWAN Fast Firmware Update Fails If any CLIPs fail, you are notified in the Firmware Update Progress dialog box: vst903.vsd 1. To review the reason for the failure, select the corresponding row. A message similar to the following might appear: Object Name: Action State: Error Id: Error Description: Error Id: 1083. Error Description : Recovery: None. $ZZWAN.#SWAN1.2 Failed 1083 Problem: A non-path error occurred.
Updating SWAN Concentrator CLIP Firmware Using the TSM Firmware Update Dialog Box to Update SWAN Firmware To stop the SWAN adapter object, you can also enter the SCF STOP command. For example: 12> SCF STOP ADAPTER $ZZWAN.#51, SUB ALL c. Check if the SWAN adapter is stopped in TSM or use the SCF STATUS SERVER command: 13> SCF STATUS SERVER $ZZWAN.#51.* 5. After the SWAN objects are stopped, try to update the SWAN CLIPs again.
Updating SWAN Concentrator CLIP Firmware List the Names of the SWAN Concentrators and CLIPs List the Names of the SWAN Concentrators and CLIPs Use the TSM Service Application or SCF to list the names of the SWAN concentrators and CLIPs in your system: • Using the TSM Service Application: VST410.vsd • Or (using SCF) enter: 4> scf names adapter $zzwan.
Updating SWAN Concentrator CLIP Firmware Check Location and Version of New SWAN CLIP Firmware Check Location and Version of New SWAN CLIP Firmware The SWAN firmware object code file is a 510 disk file that resides on a NonStop S-series server and is downloaded to the SWAN concentrator CLIP. Check the location and version of the SWAN firmware object code file for the G06.24 RVU. At a TACL prompt, enter the VPROC command: VPROC $SYSTEM.CSSnn.
Updating SWAN Concentrator CLIP Firmware • Check Firmware Version Currently Running in SWAN CLIPs Use the SCF STATUS SERVER $ZZWAN.#conc-name.clip-num, DETAIL command. For example: $SYSTEM ZWANTOOL 14> scf status server $zzwan.#s01.3, detail SCF - T9082G02 - (12JUL99) (15JUN99) - 11/17/1999 09:19:28 System \ELI Copyright Compaq Computer Corporation 1986 - 1999 WAN Manager STATUS SERVER for CLIP State :......... STARTED \ELI.$ZZWAN.#S01.3 Path A..........: CONFIGURED Path B..........
Updating SWAN Concentrator CLIP Firmware Summary of SWAN Concentrator CLIP Firmware Update Steps (Using TSM) Summary of SWAN Concentrator CLIP Firmware Update Steps (Using TSM) Required for Upgrading From T7953AAG and Later Firmware Versions Step 1: Stop the SWAN Concentrator and CLIPs Step 2: Point SWAN Concentrators to the New Firmware Object Code File Step 3: Initiate the Firmware Update Using TSM Step 4: Start the SWAN Concentrator and CLIPs Step 5: Verify That the SWAN CLIPs Are Running the Latest Fi
Updating SWAN Concentrator CLIP Firmware Step 1: Stop the SWAN Concentrator and CLIPs Step 1: Stop the SWAN Concentrator and CLIPs Use the TSM Service Application or SCF to stop the SWAN concentrators and terminate operation of all CLIPs. For example: VST420.vsd Or (using SCF), enter: 5> SCF STOP ADAPTER $ZZWAN.#S01, SUB ALL G06.
Updating SWAN Concentrator CLIP Firmware Step 1: Stop the SWAN Concentrator and CLIPs Verify That CLIPs Are Stopped Use the TSM Service Application or SCF to check that SWAN concentrators and CLIPs are in the STOPPED state. For example, to see the state of the SWAN CLIPs: VST400.vsd To see the state of the SWAN concentrators: VST422.vsd G06.
Updating SWAN Concentrator CLIP Firmware Step 2: Point SWAN Concentrators to the New Firmware Object Code File Or (using SCF), enter: 2-> status server $zzwan.#s01.* WAN Manager STATUS State :......... . . WAN Manager STATUS State :......... . . WAN Manager STATUS State :......... . . SERVER for CLIP STOPPED \ELI.$ZZWAN.#S01.1 SERVER for CLIP STOPPED \ELI.$ZZWAN.#S01.2 SERVER for CLIP STOPPED \ELI.$ZZWAN.#S01.
Updating SWAN Concentrator CLIP Firmware Step 3: Initiate the Firmware Update Using TSM Step 3: Initiate the Firmware Update Using TSM 1. Log on to the TSM Service Application. 2. Select Display> Firmware update. The Firmware Update dialog box appears. 3. From the Resource Type list, select SWAN Clip. 4. From the Display list, select All. The SWAN CLIPs are listed in the Available box: VST425.vsd 5.
Updating SWAN Concentrator CLIP Firmware Step 3: Initiate the Firmware Update Using TSM 8. In the $volume.subvolume box, enter the new firmware file location (the value you entered in the SCF ALTER ADAPTER, KERNELCODE command in Step 2: Point SWAN Concentrators to the New Firmware Object Code File). For example: VST430.vsd 9. Click OK. 10. Click Yes when a message appears, warning that you have specified a nonstandard firmware file location. 11. In the Firmware Update dialog box, click Perform action.
Updating SWAN Concentrator CLIP Firmware Step 4: Start the SWAN Concentrator and CLIPs Step 4: Start the SWAN Concentrator and CLIPs After the SWAN CLIP firmware has been updated, use the TSM Service Application or SCF to start the updated SWAN concentrator and CLIPs.
Updating SWAN Concentrator CLIP Firmware Step 1: Stop the SWAN Concentrator and CLIPs Step 1: Stop the SWAN Concentrator and CLIPs 1. Select Display>Multi-Resource Actions. The Multi-Resource Actions dialog box appears. 2. From the Resource Type list, select CLIP. 3. From the Actions menu, select Stop. 4. Select the SWAN CLIPS you want to stop and click Add or Add all. The selected CLIPs are added. Note that they are still in the Started state. VST960.vsd 5. Click Perform action.
Updating SWAN Concentrator CLIP Firmware Step 2: Check the Location and Version of the SWAN Firmware VST951.vsd 6. Select OK. 7. The Progress list shows the status of the CLIP action. Wait until all the CLIPs are stopped before proceeding. Step 2: Check the Location and Version of the SWAN Firmware In the OSM Service Connection, look under the Firmware heading in the Attribute pane for SWAN CLIPS. The location and the version of the SWAN firmware is displayed.
Updating SWAN Concentrator CLIP Firmware Step 3: Initiate the Firmware Update 5. Use the $SYSTEM.CSSnn subvolume and filename (CP7953P00) created during the most recent DSM/SCM Build/Apply. Because you have just loaded the new RVU, the SWAN firmware location should point to the correct subvolume and file version. Click OK. However, if you have performed a Build/Apply for a new SWAN firmware SPR, specify that location and select OK. 6.
Updating SWAN Concentrator CLIP Firmware Step 4: Start the SWAN Concentrator and CLIPs Step 4: Start the SWAN Concentrator and CLIPs 1. With the Multi-Resource Actions dialog box still open, from the Action list, select Start. 2. Click Add or Add all. 3. Click Perform Action. The SWAN CLIPs should start. If they do not, see the SWAN Concentrator and WAN Subsystem Troubleshooting Guide, section 4. You can also use SCF to start the CLIP or use the Actions - CLIP dialog box.
Updating SWAN Concentrator CLIP Firmware If a CLIP Fails to Update (Using OSM) c. Use the SCF STATUS SERVER command again to make sure that the SWAN adapter object is stopped. 6. In the Available Actions list, select Firmware Update to update the firmware for that particular CLIP. 7. Select Perform action. 8. Monitor the progress in the Action Status menu. To view details of the action, select Details. 9. To start the individual CLIP, select Start from the Available Actions list and select Perform action.
Updating SWAN Concentrator CLIP Firmware If a CLIP Fails to Update (Using OSM) G06.
Glossary A0CINFO file. A distribution subvolume (DSV) file that contains information about a product and each of its files, including product and file dependencies, how the files are used and where they are placed, and on which type of processor the product runs. Every product and SPR to be managed by the Distributed Systems Management/Software Configuration Manager (DSM/SCM) is distributed in a subvolume, and that subvolume must contain the product’s A0CINFO file. A1CINFO file.
Glossary CLIP CLIP. See communications line interface processor (CLIP). cluster switch. See HP NonStop™ Cluster Switch (model 6770) and HP NonStop™ ServerNet Switch (model 6780). cold load. A synonym for system load or load (in the case of single processor load). System load or load is the preferred term in this and other HP NonStop server system manuals. See system load and load. communications line interface processor (CLIP).
Glossary dynamic-link library (DLL) dynamic-link library (DLL). A collection of procedures whose code and data can be loaded and executed at any virtual memory address, with run-time resolution of links to and from the main program and other independent libraries. The same DLL can be used by more than one process. Each process gets its own copy of DLL static data. Contrast with shared run-time library (SRL). dynamic loading.
Glossary discovery discovery. For the SM package, the process of identifying the resources that exist on a NonStop S-series server. See also incremental discovery and initial discovery. Distributed Systems Management/Software Configuration Manager (DSM/SCM). A graphical user interface (GUI)-based program that installs new software and creates a new HP NonStop Kernel operating system. DSM/SCM creates a new software revision and activates the new software on the target system. DSM/SCM.
Glossary Gigabit Ethernet 4-Port ServerNet adapter (G4SA). Gigabit Ethernet 4-Port ServerNet adapter (G4SA). A multiport ServerNet adapter that provides 1000 megabits/second (Mbps) data transfer rates between HP NonStop™ S-series systems and Ethernet LANs. Global Customer Support Center (GCSC). A support organization that provides telephone and remote diagnostic support for HP customers. There are GCSCs located all over the world. See also Online Support Center (OSC). halt.
Glossary HP NonStop™ S74000 server HP NonStop™ S74000 server. The high-performance successor of the NonStop S72000 line of HP NonStop S-series servers. HP NonStop™ S76000 server. The high-performance successor of the NonStop S74000 line of HP NonStop S-series servers. HP NonStop™ S78000 server. The high-performance successor of the NonStop S76000 line of HP NonStop S-series servers. HP NonStop™ S86000 server.
Glossary HP NonStop™ System RISC Model J processor (NSR-J processor) HP NonStop™ System RISC Model J processor (NSR-J processor). The model designation for the TNS/R processor used in the HP NonStop S7800 server. HP NonStop™ System RISC Model T processor (NSR-T processor). The model designation for the TNS/R processor used in the HP NonStop S72000 server. HP NonStop™ System RISC Model V processor (NSR-V processor). The model designation for the TNS/R processor used in the HP NonStop S74000 server.
Glossary HP NonStop™ ServerNet Switch (model 6780) switch is used with star, split-star, and tri-star topologies. See also HP NonStop™ ServerNet Switch (model 6780). HP NonStop™ ServerNet Switch (model 6780). The cluster switch used in the layered topology. The 6780 switch consists of a switch logic board, a midplane, plug-in cards, power supplies, and fans. HP NonStop Open System Management (OSM) Interface. Replacement for TSM as the system management tool of choice for NonStop S-series servers.
Glossary I/O multifunction (IOMF) CRU I/O multifunction (IOMF) CRU. (1) A NonStop S-series server customer-replaceable unit (CRU) that connects the I/O enclosure to a processor enclosure, using a ServerNet cable, and that supplies power to the components within the IOMF CRU, as well as redundantly to the disk drives, SCSI terminators, and ServerNet adapters in that enclosure.
Glossary Physical view Physical view. One of several views of a server available in the view pane of the Management window of the OSM Service Connection, TSM Service Application, and OSM and TSM Low-Level Link. A Physical view of a server is a view of all the enclosures and is intended to represent the actual floor plan at the site. A Physical view of an enclosure is a visual representation of the physical placement of supported resources inside the enclosure. Planner Interface.
Glossary ServerNet/FX adapter fabric for a group. (2) A collective term for both SEBs and modular SEBs (MSEBs) when a distinction between the two types of SEBs is not required. ServerNet/FX adapter. A ServerNet adapter that logically extends the ServerNet X and Y fabrics to other clusters in a Fiber Optic Extension (FOX) ring by using fiber-optic lines. Two 6740 ServerNet/FX adapters are used, one for the X ring and one for the Y ring. ServerNet/FX 2 adapter.
Glossary site update tape (SUT) site update tape (SUT). One or more tapes that contain each target system’s site-specific subvolume and various products. Each product contains a softdoc and a complete set of files. A SUT is delivered with every new NonStop S-series server and can be ordered whenever a new RVU of the system software is available. A full SUT contains the current RVU of the HP NonStop Kernel operating system and all product software that has been ordered with it.
Glossary system console system console. A PC-compatible workstation on which the TSM or OSM Application Suite or web-based software is running. The system consoles configured as the primary and backup dial-out points are referred to as the primary and backup system consoles. system load. (1) To start the system; to load the HP NonStop Kernel operating system image into the memory of a processor. (2) RELOAD. (3) The process of loading the operating system.
Glossary Trivial File Transfer Protocol (TFTP) G06.
Index A A7CINFO files activation package 5-12 introduction, used in installation 1-4 Aborting the system startup process A-10 ALLPROCESSORS paragraph 1-15 Alternate system disk location, specifying 11-4, 11-8, A-10 AUDITTRAILBUFFER parameter, DP2 and RDF performance 12-15 B Bootstrap 6-1 Build process, DSM/SCM 5-13 Build/Apply request defined 1-6 C C7953P00 C-10, C-20 CBEXE 3-4, B-4, B-16 CIIN file 11-4, A-10 CLEANOSS macro different from FALLBACK macro 1-18 during Build/Apply 13-3 in falling back 1-19 ov
Index F mod-14 extent boundary.
Index M M merge_whatis 10-7 Mirror system disk loading system from 11-7 restarting after REPLACEBOOT 12-11 MXCI DROP command 1-30 N Native CRE/RTL product (T8431) 1-35 NETWORKS file 10-2 New software revision, DSM/SCM 5-8 NonStop ODBC Server and Client, TNOS server and TNOS utility 1-39 NonStop ServerNet Switch firmware requirements 1-9 updating firmware 12-5 NonStop SQL errors, when installing D31 DSM/SCM B-18 NonStop SQL/MX 13-5 NonStop TCP/IP, sample configuration files 12-2 NonStop TS/MP PATHMON 1-20
Index R Processor reload 11-6 Processor type 1-15 Profiles, target, changing information 5-10 PROTOCOL configuration file 12-2 file, backup copies 10-2 R RDF interoperability SPRs 3-7 Reinitializing NonStop SQL database for DSM/SCM B-18 RELOAD command (TACL) 11-6 Reload operation 11-6 REPLACEBOOT 6-1 RESCONF file 10-2 Resetting an SP 7-18 RVUs 3-1 S S7000 boot millicode 8-1 S7800 CRUs 1-32 S7x000 boot millicode 8-1 SCF CONTROL, REPLACEBOOT 6-1 Scout for NonStop Servers 3-1 SCSI boot code fallback 15-1 p
Index T SQL/MX Release 2.
Index V V v3 RTL 1-23 Verifying system operations 4-3 Visual Inspect 1-21 VPROC command 3-4, B-4 W WAN Wizard Pro Version 3.0 4-2 WANLNCK utility C-11 Windows XP Professional 1-1 Z zdsmexe, in IXF Receive B-20 ZPHIRNM PREVIEW mode 10-5 reactivating previous software revision 16-1 running 10-1, A-6 ZPHITI canceling a Build/Apply request 5-22 starting 14-2 Special Characters $AUDIT 4-10 $DSMSCM 4-10 $SYSTEM 4-10 $SYSTEM.ZTCPIP 12-1 $SYSTEM.
