H06.10 Software Installation and Upgrade Guide HP Part Number: 544422–001 Published: May 2007 Edition: H06.
© Copyright 2007 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Table of Contents About This Document.......................................................................................................11 Supported Release Version Updates (RVUs)........................................................................................11 Intended Audience................................................................................................................................11 New and Changed Information in This Edition...............................................
2 H06.10 Installation, Migration, and Fallback Considerations.................................39 Code Profiling Utilities.........................................................................................................................39 Kernel-Managed Swap File (KMSF).....................................................................................................40 IOAM and Migrating Existing Data to an Enterprise Storage System (ESS).......................................40 NonStop SQL/MX......
Safeguard Longer Password Length.....................................................................................................53 Migration.........................................................................................................................................54 Fallback in a Safeguard Environment.............................................................................................54 Fallback with Standard Security (Safeguard Not Installed).......................................
Stop Applications..................................................................................................................................90 Drain the Spooler (Optional)................................................................................................................90 Back Up the Spooler Control Files........................................................................................................91 ZPHIRNM........................................................................
Using PREVIEW Mode..................................................................................................................113 Run ZPHIRNM..............................................................................................................................114 11 Loading the Previous RVU and Resuming Normal Operations ..........................115 Alerts...........................................................................................................................................
Cancel Pending Build/Apply Requests....................................................................................136 Install the DSM/SCM Client From ZDSMSCM ..................................................................................137 Alert (DSM/SCM T6031G02/H02 Client).......................................................................................137 Determine Your DSM/SCM Client Software Version....................................................................
List of Tables 1-1 1-2 1-3 1-4 1-5 1-6 1-7 3-1 3-2 3-3 4-1 7-1 Maintenance Entity (ME) Firmware..............................................................................................26 Maintenance Entity (ME) FPGA....................................................................................................27 HP Integrity NonStop NS-Series Server Firmware .....................................................................29 H-Series ServerNet Adapters .........................................
About This Document This guide describes: • • Upgrading the initial H06.10 RVU through the use of site update tape (SUT) refreshes, if necessary. Falling back to a previous SYSnn. Supported Release Version Updates (RVUs) This manual supports the H06.10 RVU only.
UPPERCASE LETTERS Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH Italic Letters Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name Computer Type Computer type letters indicate: • C and Open System Services (OSS) keywords, commands, and reserved words. Type these items exactly as shown.
{ $process-name } ALLOWSU { ON | OFF } | Vertical Line A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times.
CALL CHECKRESIZESEGMENT ( segment-id !i , error !o !i,o ) ; In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program). For example: error := COMPRESSEDIT ( filenum ) ; !i,o !i:i In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes.
A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed. The items in the list can 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.
ZSPI-TKN-MANAGER !o token-type ZSPI-TYP-FNAME32. What This Guide Does Not Cover • System migration planning. System-wide issues involved in migrating to the latest H-series RVU are covered in: — The H06.10 Release Version Update Compendium — The Interactive Upgrade Guide 2 (IUG2) — Installing an H-series RVU from a host system to a remote or separate network-connected target system using an Expand connection or tape. See the DSM/SCM User’s Guide for information on setting up target systems.
— — • NonStop NS-Series NS16000 Hardware Installation Manual NonStop NS-Series Carrier Grade Server Manual The OSM Migration and Configuration Guide provides an overview of all OSM applications and components, how to configure and get started with OSM, and how to use the primary OSM interface, OSM Service Connection, to monitor and perform actions on system and cluster resources. Publishing History Part Number Product Version Publication Date 544422–001 N.A.
1 Overview of Installing the H06.10 RVU This chapter introduces the basic installation tools and requirements in H-series RVUs, including installing the site update tape (SUT) for a release version update revision (RVUR). For information on installing software product revisions (SPRs), see Appendix A, Using DSM/SCM to Install SPRs. SUT on DVD Beginning with the H06.06 RVU, the H-series SUT is also available on DVD. For instructions on installing the SUT from the DVD, see the IPSetup User’s Guide.
• • S-series servers. See “Managing Microcode and Firmware for Integrity NonStop NS-Series Servers” (page 25) for detailed information on updating firmware. The RCVDUMP program has two new parameters for H-series systems only, SLICE sliceId and PARALLEL. See the TACL Reference Manual for more information on syntax and usage. For H-series systems only, RELOAD has a new option OMITSLICE. The RELOAD command also includes the option NOPRIME, which is supported on both G-series and H-series systems.
NOTE: Starting with S7X-SWV2/HNSC-SWV2, comForte MR-Win6530 replaces Outside View as the terminal emulator shipped with the console software. It is launched by the OSM Low-Level Link version T0633 AAT (or later) for Startup TACL and Event Stream windows. MR-Win6530 must be installed on the system console before installing OSM Low-Level Link version T0633 (or later).
Migration Alert Starting with the H06.09 RVU, OSM no longer uses the User ID and Password to start monitoring the Maintenance Switch and UPS. For more information, see “OSM Uses Different User ID and Password to Monitor Maintenance Switch and UPS” (page 41) OSM Client-Based Components Like other system console software, the OSM client-based components are dual-threaded; that is, they support both G-Series and H-series RVUs. For H06.
DSM/SCM and the H06.10 RVU • • • • • • • • The DSM/SCM H02 PVU (T6031H02) is supported for Integrity NonStop NS-series servers only. A new type of hardware platform and selectable option, TNS/E, for Integrity NonStop NS-series servers has been added to the Planner Interface (PI) screens. See the DSM/SCM User’s Guide for configuration information. By default, the DSM/SCM H02 PVU is configured to manage OSS files. Check that OSS is configured and started if DSM/SCM is set to manage OSS files.
1. Receive new software into the DSM/SCM Archive. When software is received, the files from each product are stored in the DSM/SCM Archive, a holding area for your software. File attributes are stored in the DSM/SCM host database. Each time a new version of a product is received, only changed files are placed in the Archive, and file attributes are updated in the host database. 2. Create a new software revision.
Server SYSTEM_PROCESSOR_TYPE Integrity NonStop NS5000 NSE-P Integrity NonStop NS3000 NSE-K Also, check the CONFTEXT file to check that these entries are present.
Managing Maintenance Entity Firmware for Processor Switch and I/O Adapter Module (IOAM) There is maintenance entity (ME) firmware on the ServerNet Switch Boards located in both processor switch and I/O adapter modules. In processor switches, the maintenance entities provide functionality similar to what the service processors (SPs) do for S-series systems (including connectivity within the system and to a ServerNet cluster).
4. 5. Monitor the update. Repeat for the processor switch on the other Internal ServerNet Fabric. To use the OSM Service Connection to update the ME firmware for each IOAM: 1. 2. 3. 4. 5. Locate the ServerNet Switch Board on one IOAM (in the tree pane, select System > Group > IOAM Enclosure > IOAM > ServerNet Switch Board). Right-click the ServerNet Switch Board object and select Actions. In the Actions dialog box, select ME Firmware Update and click Perform Action. Monitor the update.
Managing Firmware in a NonStop Blade Complex NOTE: In TACL commands and event messages, you might see: • The term slice, which is equivalent to the term NonStop Blade Element (NSBE). • The term processor complex, which is equivalent to the term NonStop Blade Complex (NSBC) The OSM GUI now displays the newer Blade Complex and Blade Element terminology.
On Integrity NonStop NS-series servers, the bootstrap code is part of the NonStop Blade Element firmware and is, therefore, not on a disk. You update the disk bootstrap code on all the bootable slices (that is, those that contain logical processor 0 and 1) by using the Blade Complex Firmware Update procedure. Table 1-3 lists the updateable NonStop Blade Complex firmware and the recommended order for updating firmware through the guided procedure.
If your firmware module files are downrev, use OSM and the guided procedure to update the shadow and current firmware images (as separate operations) for each NonStop Blade Element and for each NonStop Blade Complex. Before you begin the firmware update procedure, check for any yellow or red alarms associated with a processor (blade) complex. These alarms might indicate a severe problem. You can, however, begin the firmware update if the yellow alarm is associated with a downrev firmware file.
2) NOTE: OSM will preselect all the firmware that it detects as down-rev. NOTE: Update all NonStop Blade Elements in the complex at this time. Using the Switch Blade Element Firmware Images dialog box, select Yes. CAUTION: 3) b. Do not reset the NonStop Blade Elements after this step. Repeat steps 1 and 2 for the other NonStop Blade Complexes. Halt and then power cycle all processors: 1) Using OSM Low-Level Link, halt all the logical processors in the system.
1. 2. 3. 4. 5. 6. In the tree pane of the OSM Service Connection, right-click the Blade Complex resource. From the shortcut menu, select Actions. When the Actions window appears, select Firmware Update from the Available Actions list. Click Perform action. In the guided procedures interface, click Start in the Procedure Tasks List pane. Follow and complete the guided procedure dialog boxes using this summary: a.
NOTE: Before connecting a NonStop S-series system to an Integrity NonStop NS-series system through legacy I/O, you must first update the firmware for both the S-series Gigabit 4-port ServerNet adapter (G4SA) and the Fibre Channel ServerNet adapter (FCSA). Firmware for both the G4SA and FCSA adapters used for S-series systems is not initially compatible with Integrity NonStop NS-series systems.
• G4SA. The OSM Service Connection displays G4SA firmware attributes and action under the G4SA SAC object. To check or update G4SA firmware, locate and expand the G4SA, then select its subcomponent G4SA SAC object. In the following example, the firmware attributes show that the current firmware Version is the same as the available Default File Version; no update is necessary.
Table 1-4 H-Series ServerNet Adapters (continued) Product Number Description Default Location Tool Related Information T0612G06 ^ AAB FCSA flash VIO enclosure C0612R00 boot firmware SYSnn subvolume OSM SC or SCF Versatile I/O Manual T0612G06 ^AAB G4SA firmware SYSnn subvolume OSM SC or SCF Versatile I/O Manual Host FRU Disk File Name VIO enclosure C0612R00 Managing SWAN and SWAN 2 Concentrator Firmware Both SWAN and SWAN2 are supported in H-series RVUs and OSM is used to update the firmwar
Table 1-6 Updateable Firmware for the NonStop ServerNet Switch (continued) Product Number T2819 AAB Description Host CRU/FRU Disk File Name Cluster switch 6780 LBC2819 firmware ServerNet (FPGA** for Switch (FPGA) hardware monitoring) Default Location Tool SYSnn subvolume SCF; OSM SC Related Information ServerNet Cluster 6780 Operations Guide *ASIC (application-specific integrated circuit)**FPGA (field-programmable gate array) Backing Out the DSM/SCM Revision If you encounter a problem with a SUT r
Product Name G-series Product ID T-Numbers NonStop XSLT Translator SX22V2 T0592 (not moving to H-series)T0601 NonStop SOAP Client SX24V1 T0624 NonStop Fast XML Parser SX25V1 T0625 1 NonStop Pathway/iTS with TS/MP (SR76V1) in S-series becomes NonStop Pathway with TS/MP in NS-series.
2 H06.10 Installation, Migration, and Fallback Considerations See the Readme file and the appropriate softdocs for the latest information on any migration or configuration steps.
tools, applications must be compiled using the H06.07 or later versions of the TNS/E native compilers. The SPR levels of these compilers are: Compiler Minimum SPR Level TNS/E COBOL T0356H01^AAI TNS/E C/C++ T0549H01^AAD TNS/E pTAL T0561H01^AAC Native c89 utility T8164H01^ABE These compiler versions provide the required command line options for running the Code Coverage utilities. Starting in the H06.
NonStop SQL/MX NonStop SQL/MX Release 2.3, which has no G-series equivalent, introduces this functionality: • • • • Provides an online variant of the POPULATE INDEX and MODIFY utilities Generates modules files in Guardian directories Projects only the requested number of rows from the table instead of scanning the complete table Introduces a new Control Query Default statement (CQD) NonStop SQL/MX Release 2.3 is interoperable with compatible releases of NonStop SQL/MX.
OSS Large Files Starting with the H06.06 RVU, OSS files larger than the previous 2 GB limit (large files) are supported. The OSS file system and utilities are able to handle file sizes up to 1 terabyte. To implement this capability, the OSS file system and utilities are modified to support Format 2 files (previously, all files were created as Format 1). All large files are created as Format 2; small files (less than 2 GB) can be created as either Format 1 or Format 2.
file created using this SPR. The DSAPDDL file for T9543H01^ABH contains these changes to the directory-record structure: • • The field named fifth is changed from type binary unsigned to type binary 32 unsigned. These fields are added to the end of the structure: — Field flab2_flags1 of type binary unsigned identifies OSS files larger than 2 GB. — Field ext-0-fsu of type binary unsigned contains the extent size of large OSS files for extent number 0.
If a Format 2 file does cause a program to fail, the programmer can do one of the following: • • Change the program to accept Format 2 files. Protect the program by converting the file to Format 1 using the following commands: FUP CREATE TEMP, FORMAT-1, TYPE U, CODE 180, & EXT (28,1400), MAXTENTS 749 FUP COPY MYFILE, TEMP FUP PURGE MYFILE FUP RENAME TEMP, MYFILE • Protect the program by creating a Format 1 file, then appending the desired data to the file.
Installing OSS Products Not Managed by DSM/SCM Use COPYOSS or PINSTALL or both to install products that are not managed by DSM/SCM. • • If any OSS files are managed by DSM/SCM, use PINSTALL on the remaining pax archives. See the OSS Management and Operations Guide for a description of PINSTALL use or the pinstall(1) reference page in the OSS Shell and Utilities Reference Manual. If no OSS files are managed by DSM/SCM, use COPYOSS for all of the OSS pax archives in the ZOSSUTL subvolume.
Pathway/iTS 1.1 The H06.10 RVU introduces Pathway/iTS 1.1. Pathway iTS\1.1 supports the following new SCOBOL statements: • • • • DIALOG-BEGIN DIALOG-SEND DIALOG-ABORT DIALOG-END These statements enable users to send more than 32000 bytes of data to the same Pathway server using a context-sensitive communication model. These new features are provided by the PathTCP4 (T0700) component of Pathway/iTS. Migration Pathway/iTS 1.1 includes both PathTCP3 and PathTCP4. PathTCP3 is unchanged.
Remote Database Facility (RDF) The version of the NonStop Remote Database Facility (RDF, T0346) on H06.10 is compatible only with the AAZ SPR of RDF on NonStop S-series systems. HP Tandem Failure Data System (TFDS) HP Tandem Failure Data System (TFDS) is available on the NonStop Series TNS/E platform and provides hardware, software, and subsystem failure analysis and automated processor reload and dump capabilities.
Visual Inspect Restart $IMON Required If you use Visual Inspect, you must restart the Inspect Monitor process ($IMON) every time you restart the system. Upgrading Visual Inspect Client to Version 3.x If you are currently running Visual Inspect client version 2.x, upgrading to version 3.x is optional. However, to get the full benefit of the features and performance of the H-series Visual Inspect servers and client, you must upgrade to Visual Inspect client version 3.x.
Since the new T-number T0744 is replacing the previous T27nn T-numbers, click Continue without selecting any of the T27nn T-numbers. DSM/SCM will remove those T-numbers from your configuration and install T0744. Fallback SPR Required for OSS Large Files If you are falling back to H06.05, install the Backup and Restore 2 SPR T0744H01^AAA to restore files smaller than 2 GB. Files larger than 2 GB are skipped. T0744H01^AAA does not support pre-H06.05 RVUs.
NOTE: You must transfer the TNS/R object files to a TNS/R system for execution; you cannot execute them on the TNS/E system. The H-series TNS/R compilers and tools have all the features and functionality of the G06.20 and later G-series products. TNS/R compilation on H-series systems is supported only for G06.20 and later G-series RVUs. For more information about support for G-series tools on H-series systems, see the H-Series Application Migration Guide or the individual manuals for the tools.
T9228 ZZOSSWFSRL Filesys Libraries T9627 ZOSSESRL OSSFSLIB T9661 ZUTILSRL MC Runtime Library T8888PAX OSS packaging for all the preceding For reporting problems with any of these SRLs in H-series systems, you should specify the new T-number T8888. The fix will be available via T8888. If you do report a problem against the old T-number (for example, T8432 for ZCRTLSRL), the fix will still be available via T8888.
L/USERID is marked as expired as of that date. For a new user added to the system after the algorithm is changed to HMAC256, the password in L/USERID file is deleted. Migration in a Safeguard Environment The following procedure is intended to handle any unexpected failures that might occur during Safeguard migration. The procedure preserves the user/password database, which is necessary to restore the original system user/alias database. 1.
4. Users are prompted to change their password when logging into the system if: • Their user account existed before the installation of the H03 version of Safeguard, or • They are new users and their password was encrypted in DES or not encrypted at all before PASSWORD-ALGORITHM was changed to HMAC256. When prompted, users should enter and re-enter a new password and log onto the system as usual. 5.
Migration Users migrating to a version of Safeguard and Standard Security that supports longer passwords should be aware that two new attributes are introduced: PASSWORD-COMPATIBILITY-MODE and PASSWORD-MAXIMUM-LENGTH. The default setting for PASSWORD-COMPATIBILITY-MODE is ON, meaning that new passwords are limited to 8 bytes. To enable the longer password feature, PASSWORD-COMPATIBILITY-MODE must be set to OFF, and the existing PASSWORD-MAXIMUM-LENGTH attribute must be set to a value greater than 8.
Safeguard Password Quality Enhancements The T6533H04^ABM and later versions of Standard Security and the T9750H04^AFC and later versions of Safeguard, initially released with the H06.
OSI FTAM and MHS Longer Password Support Starting with the H06.10 RVU, the OSI FTAM (T6982) and MHS (T7937) products support passwords up to 64 bytes long. The passwords can also include special characters. To use these features, the Standard Security T6533H04 SPR must be installed. Compiler Default Change for Object Code Generation Prior to the H06.08 RVU, the native C/C++, COBOL, and pTAL compilers generated preemptable object code by default. Beginning in H06.
Library, T1269H02 for CRE) provide a subset of new features from the new ISO/IEC 9899:1999 standard. Applications that use the new run-time library features will not run on RVUs prior to H06.08 unless the new run-time library SPRs are applied. Applications that use the new compiler features cannot be recompiled on RVUs prior to H06.08 unless the new C compiler SPRs and standard header SPR are applied.
3 Upgrade Checklist Use the checklist in Table 3-1 as you perform the tasks required to upgrade to the H06.10 RVU and the checklist in Table 3-2 (page 60) to record the information needed when performing these tasks. Table 3-3 (page 61) lists SPRs that should be installed before upgrading to H06.10. NOTE: Minimum duration for tasks is not documented for H06.10. You might have to update the service processor (SP) firmware on NonStop S-series systems for IOMF2 PMF customer-replaceable units (CRUs). H06.
Table 3-1 H06.10 Upgrade Checklist (continued) Task Description Reference Done? 18. Recover the TCP/IP files (if necessary). “Update NonStop TCP/IP Configuration Files” (page 103) 19. Check processor status. “Check Processor Status ” (page 65) 20. Co nfigure WANMGR (if necessary). “Configure the WAN Manager” (page 106) 21. Update SWAN concentrator CLIP Appendix C: “Updating SWAN Concentrator CLIP firmware (if necessary). Firmware” 22. Start system and application software.
Table 3-2 H06.10 Required Information Checklist (continued) Type of Information Value ServerNet Cluster firmware DSM/SCM product version (server and client) Processor type H06.10 Fallback SPR Summary Table 3-3 Recommended Fallback SPRs Fallback SPR Current RVU Requires Coldload? For More Information T9050AQM (DP2) pre-H06.05 Yes See “DP2” (page 42) T9543ABH (DSAP/DCOM) pre-H06.06 No See “DSAP/DCOM” (page 42) T0744 (Backup/Restore 2) No See “Backup/Restore 2” (page 48) H06.
4 Preparing to Upgrade the Server Software (Preinstallation Tasks) This chapter describes tasks that are needed before updating the system console and receiving the SUT.
Back Up TMF Files Use the OBEYFORM option available in TMFCOM INFO commands to save current configuration information in command files. 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 H06.10 RVU. At a TACL prompt, issue the status command to determine the current SYSnn subvolume.
• • “Check the Status of the Spooler Collector” (page 69) “Check for Sufficient Swap File Space” (page 69) Check Processor Status 1. Log on to the OSM Low-Level Link. The OSM Low-Level Link Application appears. 2. Select Processor Status. The Processor Status dialog box appears. The Processor Status for all processors should be Executing NonStop OS. Check System Components 1. Log on to the OSM Service Connection. See the OSM Migration and Configuration Guide if you have any problems accessing OSM.
The System Status window indicates the overall health of a system by the color of the system icon. From the Summary menu, select System Status. Yellow indicates a possible system problem. For example: 2. Double-click to expand the object further to identify components that require attention (yellow or a yellow arrow) or immediate service (red). CAUTION: If a red triangle appears over an object, or if any component is highlighted in red, contact your service provider. 3. 4.
NOTE: If the Halt Code or Halt Flag attributes do not match these values, see the Processor Halt Codes Manual. Verify the State of the Internal ServerNet Fabric To verify that the paths and connections within the ServerNet system area network (ServerNet SAN) are properly functional: 1. 2. 3. 4. 5. 6. 7. 8. Log on to the OSM Service Connection. In the tree pane, double-click the Fabric Group. For each Internal ServerNet Fabric, double-click the fabric. Select each Processor Switch Power Supply.
> SCF LISTDEV $ADBIT RESULTS 18> scf SCF - T9082H01 - (01MAY05) (15MAR05) - 05/09/2005 16:13:56 System \ATLAS (C) 1986 Tandem (C) 2003 Hewlett Packard Development Company, L.P. (Invoking \ATLAS.$SYSTEM.STARTUP.
STORAGE - Status DISK \ATLAS.$ADBIT LDev Primary Backup Mirror 150 *STARTED STARTED MirrorBackup *STARTED STORAGE - Status DISK \ATLAS.$ADSAV LDev Primary Backup Mirror 149 *STARTED STARTED Total Errors = 0 $SYSTEM TOOLS 49> STARTED MirrorBackup STOPPED STOPPED Primary PID 0,331 Backup PID 1,290 Primary PID 0,330 Backup PID 1,291 Total Warnings = 0 Verify Tape Drives (If Necessary) You can use SCF commands or OSM to obtain status information about a tape drive.
1. At a TACL prompt, start NSKCOM: $SYSTEM STARTUP 5> nskcom NSKCOM - T5838H01 BASE (01OCT04) - Apr 15 2005 Copyright 1995 Compaq Computer Corporation $SYSTEM.SYSTEM.ZSYSCFG KMS.SWAPFILE = 0 $SYSTEM.ZSYSSWAP.SWAP00 KMS.SWAPFILE = 1 $SYSTEM.ZSYSSWAP.SWAP01 KMS.SWAPFILE = 2 $SYSTEM.ZSYSSWAP.SWAP02 KMS.SWAPFILE = 3 $SYSTEM.ZSYSSWAP.SWAP03 2. Issue the STATUS SWAPFILE * command to display the peak pages reserved so that you can compare that information to the total amount of swap space available.
Table 4-1 lists the specific SPRs required for compatibility and interoperability between Integrity NonStop NS-series systems and NonStop S-series systems. Table 4-1 Interoperability SPRs for NonStop NS-Series and NonStop S-Series Systems Minimum SPR Product Name Description Introduced in this RVU T0294 AAP SNETMON Required for ServerNet clustering G06.26 T9205 ACF TACL Required for remote NEWPROCESS of OCA objects G06.26 T9621 ABB Binder Required to recognize OCA G06.
5 Installing a SUT for the H06.10 RVU Installing a new RVU or a SUT involves these DSM/SCM tasks: 1. 2. 3. “Receive New Software Into the Archive” (page 73) “Create a New Software Revision” (page 77) “Build and Apply the New Software Revision” (page 80) Alerts for Installing a SUT Do not use this procedure to upgrade more than one Integrity NonStop NS-series servers at a time or to install SPRs. For SPRs, see Appendix A, Using DSM/SCM to Install SPRs.
startscm NOTICE: * * * * If the hometerm chosen during INITENV, $zhome, is not currently in a paused state, STARTSCM and DSM/SCM server processes may hang indefinitely.
7. In the Options group box, click Input source. The Request Source Options dialog box appears. 8. 9. Select Tape drive. From the list, select the tape drive that contains the SUT, and click OK. The Request Source Options dialog box closes. 10. In the Options group box of the Receive Software Request dialog box, click Scheduling. The Request Scheduling Options dialog box appears. Make the appropriate selections and click OK. The Request Scheduling Options dialog box closes. 11.
• EMS event messages to see if a cartridge on a nonautoloading drive of the SUT needs to be mounted. EMS messages are displayed in these windows: — The EMS Event Stream window — The EMS Events window displayed by DSM/SCM when you click Show EMS events from the Status window You can also check the Requests window to ensure that the request is finished. (Select Requests>Requests list.) For example: 13. When the request is finished, close the Status and Requests windows. 76 Installing a SUT for the H06.
14. Update the Software in Archive dialog box to show the newly received SUT. Select Window>Refresh. The new SUT appears in the window. 15. Keep the Planner Interface open for the next task. Create a New Software Revision When you create a new software revision, DSM/SCM selects the products in the SUT that are licensed for your site and replaces any previous versions of the products. The following steps assume that you are creating a new software revision that manages OSS files.
b. c. Click Output to view the default output values. Enter the appropriate values in the data fields. NOTE: On H-series systems, the alternate name for the $SYSTEM drive now defaults to $FC1 for fibre channel drives or $SCSI for SCSI drives. If this default has been changed, then the target volume specified in the Planner Interface for new subvolumes must reflect this change. d. 3. 4. 5. Click OK. DSM/SCM returns you to the Target Information dialog box.
c. d. 6. Add a description describing the new software revision (such as H06.10 SUT) and click OK. In the Software in Archive window, select the H06.10 SUT that was just received into the archive and click Copy to.
You can retain non-SUT or third-party products from your current configuration into the new revision: • • To include one or more products in the configuration to be built, select the products and click Continue. To include all products, click Select All and click Continue. The New software revision list now displays the new revision level (H06.10.nn). For example: 7. Keep the Planner Interface open for the next task.
1. In the New software revision dialog box, click Build/Apply to display the options for your Build/Apply. It might take several minutes for DSM/SCM to assemble the build information. During this time, the Build/Apply Request dialog box options and commands are dimmed and unavailable. When the Build information is assembled, the Build/Apply Request dialog box is refreshed. It displays default options and assigns a name to the Build/Apply request. For example: 2. 3.
8. (Optional) Confirm that the spooler is active and not 100 percent full before executing the Build/Apply request. At a TACL prompt, start SPOOLCOM and issue a COLLECT, STATUS command. For example: 12> spoolcom $spls; collect, status COLLECT $S 9. 82 STATE ACTIVE FLAGS 3 , CPU 1 PRI 154 In the Build/Apply Request dialog box, click OK. Installing a SUT for the H06.10 RVU UNIT 4 DATA FILE %FULL $OPS0.SPL.
DSM/SCM runs the Build and Apply steps and displays a Status window, which is automatically updated at regular intervals.
10. Check EMS messages for more detailed information about your Build/Apply: a. In the Events window, click Refresh to see newer messages. b. When finished viewing, click Close. NOTE: If you encounter any problems, see the DSM/SCM User’s Guide or online help. When the Build/Apply finishes successfully and a snapshot is received into the host database: • 84 The Request activity summary in the Status window shows that the Build, Apply, Create snapshot, and Receive snapshot activities finished.
• • The last message in the EMS Events window shows that the input snapshot finished successfully. The Requests window shows that the request is finished. (Select Requests> Requests list). 11. Close the EMS Events, Status, and Request windows. 12. Exit the DSM/SCM Planner Interface. Print Operator Instructions From the Target Interface (ZPHITI) Print the operator instructions that you edited. 1.
(c) Hewlett Packard Development Company L.P., 1994-2004 All Rights Reserved ============================================================================== F1-Logon F8-Clear entry F15-Help SF16-Exit Ready 2. Enter your user ID or alias (if necessary) and password and press F1 to log on to the Target Interface.
DSM Software Configuration Manager Target Menu - Select Action ============================================================================== \WARRIOR Prior snapshot 2003-11-20:12:18:44 DEFAULT Last S/W applied on SYS 00 on 2002-11-22:12:17 Selection number: ============================================================================== Choose an action by entering the selection number of an item from the list below.
You will run merge_whatis after using ZPHIRNM. If you have OSS configured to run the OSS merge_whatis utility automatically, you can ignore running merge_whatis. Recovery for Problems Installing an H06.10 SUT or SPRs 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.
6 Running ZPHIRNM During the Build/Apply phase, DSM/SCM places product files in their subvolumes with temporary (fabricated) file names so that new file names do not conflict with the file names of currently running programs. This chapter describes how to run the ZPHIRNM program on the target system to: • • Rename the files that currently have actual file names with fabricated names. These files become obsolete when the new files are renamed.
• • • • • • • • DNREVBAK HOSTS NETWORKS PORTCONF PROTOCOL RESCONF SERVICES SMTPCONF The file names of NonStop TCP/IPv6 that reside on the SUT are: • • • • • • ztcpip.smplhost ztcpip.smplprot ztcpip.smplnetw ztcpip.smplport ztcpip.smplresc ztcpip.smplserv Stop Applications Before running ZPHIRNM: 1. Stop DSM/SCM if it is still running. For example: > VOLUME $dsmscm_vol.
stops when it has no more open jobs. Each print process finishes printing active jobs and then stops. After all collectors and print processes have stopped, the supervisor process stops itself. The spooler enters the dormant state, ready to be warm started. CAUTION: Never use the TACL STOP command to halt the spooler. The control file can be corrupted during the next warm start or rebuild.
Files Files Files Files Files processed in renamed from renamed from renamed from renamed from obsolete TSVs ............................... real name to fabricated name ................ fabricated name to real name ................ real name to fabricated (ZPG) name .......... fabricated name to fabricated (ZPG) name .... 14 23 0 0 0 Total Number of files renamed .................................. ------23 Number of files renamed back during undo processing ............
ZPHIRNM begins processing and provides status of its progress. 4. If necessary, you can compare the creation dates of the whatis file to the whatis_old file to see if changes occurred: a. Run the more command against the whatis file: more b. c. /usr/share/man/whatis After reviewing the displayed file, exit by entering the letter q at the percentage (%) prompt. Repeat Steps a. and b. for the whatis_old file. Verify That ZPHIRNM Ran Successfully 1. 2. Review the log file.
7 Loading the H06.10 RVU This chapter describes how to perform a system load of the H06.10 RVU of the NonStop operating system into the memory of each processor in an Integrity NonStop NS-series server. NOTE: For detailed information on performing a system load of an Integrity NonStop NS-series server, see Chapter 15 in the NonStop NS-Series Operations Guide. By default, one $SYSTEM is already configured.
• • Mirror 110 3 1 2 1 1 Mirror Backup 110 2 1 2 1 1 A SCSI-Load attempts to load the system from a disk in group, module, slot 11.1.11 of a NonStop S-series I/O enclosure. See Table 7-1 (page 95). You can configure additional alternate system disks. To create an alternate system disk, see the NonStop NS-Series Hardware Installation Guide. Then use OSM to make the disk available in the Configuration Drop-down menu in the System Load dialog box.
The command interpreter input (CIIN) file is automatically invoked after the first processor is loaded. The CIIN file contains the TACL RELOAD * command, which loads the remaining processors. For details on load paths, see: • • • NonStop NS-Series NS1000 Hardware Installation Manual NonStop NS-Series NS14000Hardware Installation Manual.
Two windows for startup event stream windows (CNSLS) and two starup TACL windows (CLCIs) are automatically lauhcned. It might take a few seconds before the windows appear. NOTE: If you are using OSM Low-Level Link version T0633 AAT (or later), all four windows are contained within a single MR-Win6530 session window (as opposed to the four separate OutsideView sessions launched by earlier versions of the Low-Level Link.
SYSTEM STARTUP COMPLETE, NSK RUNNING ON PROCESSOR n 7. If the system load fails, look for halt codes or messages displayed in the Detailed box on System Startup dialog box. For recovery procedures, see the Processor Halt Codes Manual or Operator Messages Manual. Completing the System Load (If Necessary) Loading the processors with the CIIN file is usually automatic.
2. 3. Close the Processor Status dialog box. Verify that the NonStop operating system is working properly: a. Check the startup TACL window to verify that the startup scripts completed successfully. b. Check the startup event stream window and the startup TACL window for error messages. 4. Close the System Startup dialog box. For more information on system loads, the NonStop NS-Series Operations Guide. 100 Loading the H06.
8 Resuming Normal Operations This chapter describes tasks that might need to be performed after a system load. 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 for NonStop SQL/MP 1.
Start DSM/SCM 1. From the ZDSM/SCM subvolume, start DSM/SCM: > RUN STARTSCM Because the $ZHOME reliable home-term process is not an interactive process and is always paused, no action is necessary. 2. Press Enter. STARTSCM automatically runs the IP6031 TACL macro. This step can take several minutes. Run merge_whatis After coldloading the system, run the OSS merge_whatis command. (ZPHIRNM notifies you if you need to run it.
Configure Specific Products (Post-System Load) This section contains information about the configuration of various products such as OSS and SMF. See product-specific documentation for more information on installation and configuration. Update NonStop TCP/IP Configuration Files NOTE: You must have all the NonStop TCP/IP configuration files in your $SYSTEM.ZTCPIP subvolume. Otherwise, applications dependent on proper network connections will fail. Alerts: • • • See “Back Up (Copy) Files in the $SYSTEM.
Step 2: Check the CAUTION: Even if you are running TCP/IPv6 in IPv4 or conventional TCP/IP mode, you must make sure that the PROTOCOL file contains ipv6 and icmpv6 entries. If these entries are absent, a network failure might occur because the new socket routines present in TELSERV, LISTNER, and FTP access the entries in the PROTOCOL file. PROTOCOL File (Optional) If the PROTOCOL configuration file exists in $SYSTEM.ZTCPIP, you must add two lines from the sample PROTOCOL file (SMPLPROT).
phiwsock 1089/tcp #DSM/SCM Planner Interface For DSM/SCM, the port number is user-definable. The setup default is 1089. In the ZDSMSCM subvolume, check the INITSTAT file for the recently configured TCP/IP port number. INITSTAT is created by DSM/SCM when INITENV is run. Configure OSS See the Open System Services Management and Operations Guide and the Open System Services Installation Guide for information about updating and maintaining OSS database files.
Configure SMF (Optional) If you plan to configure SMF, an optional product, note: • • • Migration of data from direct volumes to SMF logical volumes is documented in the Storage Management Foundation User's Guide. Performance-critical applications that optimize the physical location of their data might need to specify the PHYSVOL option when creating data files, instead of relying on the SMF file-placement algorithm. NonStop SQL/MP 3.x must be up and running before you start SMF.
9 Backing Out the DSM/SCM Revision This chapter describes: • • Products that might have fallback implications. Before falling back or backing out the revision, review the appropriate product softdocs. Using DSM/SCM to back out the revision. Products That Might Have Fallback Implications Review the H06.10 Release Version Update Compendium and product softdocs to make sure that your installed products do not have migration implications.
You will use the spooler to print out operator instructions when backing out the revision. 2. Start the TMF subsystem and DSM/SCM if they are not already running. For example: 4> TMFCOM START TMF 5> volume $dsmscm_vol.ZDSMSCM 6> RUN STARTSCM where $dsmscm_vol is the DSM/SCM volume. Start the Target Interface (ZPHITI) 1.
Submit a Backout Request 1. From the ZPHITI Main Menu, enter 3 (Perform target activities) in the Selection number field, and press F1.
DEFAULT Last S/W applied on SYS 00 on 2000-04-14:18:01 Snapshot location: \ELI.$SPR09 ============================================================================== ATTENTION - This request is not reversible. Once the current configuration for this target is backed out, it cannot be made current again.
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 complete.
Backing Out the DSM/SCM Revision
10 Running ZPHIRNM to Reactivate the Previous Software Revision This chapter 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.
Run ZPHIRNM 1. At a TACL prompt, enter from the DSM/SCM subvolume: > RUN ZPHIRNM $vol.SYSnn where: • • $vol specifies the default current system load volume, usually $SYSTEM. SYSnn specifies the SYSnn subvolume named previously in the backout request. For example: > RUN ZPHIRNM $system.SYS00 2. 3. 4. When asked if you want to use a log file with the session, type Y and press Enter. When prompted, type a file name for the log file, and press Enter.
11 Loading the Previous RVU and Resuming Normal Operations This chapter describes how to perform a system load of the previous RVU of the NonStop operating system into the memory of each processor in an Integrity NonStop NS-series server. Alerts Before performing a system load: • Before halting the processors, stop running applications, including TMF. NOTE: • • • • To stop TMF, at a TACL prompt, enter: Do not close the System Startup dialog box while startup is in progress.
a. b. In the SYSnn field, enter nn, which is the number of the system subvolume that contains the version of the operating system you will load. Under SYSnn and CIIN Option, verify that the CIIN Disabled check box is unchecked. The CIIN file must be enabled because it contains commands needed to start the server. The startup TACL process performs the commands in the CIIN file and then logs off. For a description of the CIIN file, see the NonStop NS-Series Planning Guide. 3.
where nn is the processor number of the processor you want to reload. If the reload is initiated successfully, this message appears in a startup TACL window on the system console screen: Install Specific OSS Files (If Necessary) For those products that are not managed by DSM/SCM, you must install them using COPYOSS or PINSTALL or both. For details, see “Install Specific OSS Files Using COPYOSS or PINSTALL” (page 105).
NOTE: In the Select Firmware Modules for shadow image dialog box, select all parts that are noted as Up-Rev. NOTE: 2) Update all NonStop Blade Elements in the complex at this time. Using the Switch Blade Element Firmware Images dialog box, select Yes. CAUTION: 3) b. Do not reset the NonStop Blade Elements after this step. Repeat steps 1 and 2 for the other NonStop Blade Complexes. Halt and then power cycle all processors: 1) Using OSM Low-Level Link, halt all the logical processors in the system.
1. 2. 3. 4. 5. 6. In the tree pane of the OSM Service Connection, right-click the Blade Complex resource. From the shortcut menu, select Actions. When the Actions window appears, select Firmware Update from the Available Actions list. Click Perform action. In the guided procedures interface, click Start in the Procedure Tasks List pane. Follow and complete the guided procedure dialog boxes using this summary: a.
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 (by using Scout for NonStop Servers, for example) that the SPR can be installed on that specific H-series RVU. See the H06.
Keep a copy of each SPRNOTE and record the status of the related SPR. For example, record whether the SPR is not applicable, is already installed, or needs to be installed. Install SPRs With DSM/SCM The steps for using DSM/SCM to install SPRs are basically the same as those for installing a SUT. Save the Current Configuration First, save the current system configuration database CONFIG file. Use the SCF SAVE command: 1. At a TACL prompt, start SCF: 2> SCF 2. List the saved configuration files.
OSIMAGE 3. 0 57393152 05APR2000 8:56 255,255 NUNU 200 200 At a TACL prompt, enter a STATUS 0,0 command to see which SYSnn subvolume is currently being used: 3> status 0,0 System \ELI Process Pri PFR %WT Userid Program file 0,0 201 P R 000 255,255 $SYSTEM.SYS01.NMONTOR Swap File Name: $SYSTEM.#0 Hometerm $YMIOP.#CLCI Receive the SPR Into the DSM/SCM Archive Before Starting DSM/SCM 1. Start TMF if it is not already running: > TMFCOM START TMF Bring the SPR Into the DSM/SCM Archive 1.
1. In the New software revision dialog box, click Build/Apply to list options for your Build/Apply. The Build/Apply Request dialog box appears with all selections dimmed and unavailable. In a few minutes, the dialog box is refreshed with defaults selected. 2. Select Build (if not connected to an Expand network) or Build, apply & process snapshot (if connected to an Expand network). Include in the activation package either only changed files or all files.
> RUN ZPHIRNM $vol.SYSnn where: • $vol specifies the default current system load volume, usually $SYSTEM. • SYSnn specifies the current or new (depending on whether SYSGEN was required) SYSnn subvolume. For example: > RUN ZPHIRNM $system.SYS00 2. 3. When asked if you want to use a log file with the session, enter Y and press Enter. When prompted, enter a file name for the log file. ZPHIRNM issues this message and begins processing: Log file is open, Zphirnm will now begin processing. 4. 5.
tacl> rename newnres, oldnres 5. Run INSTALL^TEMPLATES to create updated template files: tacl>install^templates newres newnres $system.ztempl NOTE: Running this macro permanently changes the location of the EMS template files. DSM/SCM creates new EMS templates when it creates a new SYSnn. However, when the new system is loaded, the old template files named in the last execution of INSTALL^TEMPLATES are opened instead of the new files.
6. 7. 8. Click OK when asked if you are sure you want to halt. When the Action Status box confirms that all the processors have been halted, close the Processor Status dialog box. Do not log off the OSM Low-Level Link. Perform a System Load A normal system load consists of loading the operating system from disk into the memory of processor 0 or processor 1. See Chapter 7 (page 95), for information on performing a system load.
B Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software NOTE: • For Integrity NonStop NS-series servers, you must have installed both the DSM/SCM SPR and the corresponding client version before you receive an RVU SUT. For H06.10, all newly shipped Integrity NonStop NS-series servers will have the latest DSM/SCM SPR installed. The latest DSM/SCM client version is available only on the SUT unless you have ordered new system consoles.
Copyright 2004 Hewlett-Packard Development Company, L.P. $DSMSCM.ZDSMSCM.TAEXE Binder timestamp: Version procedure: Version procedure: Target CPU: OCA timestamp: Privileged code: \DRP08.$DSMSCM.ZDSMSCM 4> 1DEC2005 16:31:25 S7032H06^01OCT2004^SWARCCP^H01 T6031H02_01NOV2005_16DECABQ UNSPECIFIED 16DEC2005 16:36:28 YES Determine the Latest SWID Product Using the VPROC command, determine the SWID PVU: \DRP08.$SYSTEM.
Copy (RESTORE) the H02 DSM/SCM Product Version to Disk (If Necessary) To copy the H02 product version of DSM/SCM and the SWID product from the H06.10 RVU to disk, at a TACL prompt, enter the RESTORE command: >RESTORE/OUT $S.#nnn.DSM/$tape, ($*.E6031H02.*, *.E9298H02.*), VOL $DSMSCM, LISTALL where nnn is the RVU number (H06) and where $tape is the name of the tape drive containing the H06.10 RVU. Receive the H02 SWID and DSM/SCM SPRs 1. 2. 3. 4.
10. Click OK to run the request immediately. (The request takes less than 5 minutes to finish.) The Status dialog box appears. Wait until the display for the Request activity summary appears as Complete, and then close the Status window. For example: 11. Select Window>Refresh to update the Software in Archive dialog box to include the received software. Create a New Software Revision for H02 DSM/SCM and SWID SPRs 1.
Build and Apply the DSM/SCM H02 Software Product Revision The Build process creates an activation package of products contained in the new software revision. During the Apply process, the activation package is transferred to the target system. When the Apply request is finished, a snapshot is automatically created and returned to the host. Because you are building and applying only a few files, it should take less than an hour before the Build and Apply requests are finished and the snapshot is returned.
6. 7. To confirm that the Build and Apply tasks finish successfully and that a snapshot has been received into the host database, wait until the status shows that all requests are complete. Select Window>Refresh. The Configurations Revision dialog box is refreshed and shows the new software configuration revision containing the H02 DSM/SCM SPR. Rename the Applied DSM/SCM H02 Files By Running ZPHIRNM 1. Stop DSM/SCM: > VOLUME $dsmscm_vol.ZDSMSCM > RUN STOPSCM where $dsmscm_vol is the DSM/SCM volume. 2.
> TMFCOM STATUS TMF 2. 3. Verify your current configuration against the cold start configuration in PATHHOST (or PATHTARG) to check that the current configuration reflects all changes you have made. If necessary, run the PATHCOLD macro from the ZDSMSCM subvolume to cold start the Pathway configuration. Start DSM/SCM 1.
This example shows the H02 product version of DSM/SCM after DSM/SCM has been activated. (Bold lettering is used to show the VPROC command and the latest version): \DRP08.$DSMSCM.ZDSMSCM 2> vproc cbexe VPROC - T9617H01 - (01 OCT 2004) SYSTEM \DRP08 Date 16 Jan 2007, 18:20:02 Copyright 2004 Hewlett-Packard Development Company, L.P. $DSMSCM.ZDSMSCM.
NOTE: If you cannot cancel the Build request through the DSM/SCM Planner Interface, use the DSM/SCM Target Interface (ZPHITI) to cancel the request. See the DSM/SCM User’s Guide and online help for more information. 3. Using the Planner Interface, rename the old software inputs: a. In the Software in Archive dialog box, select the software input. b. Select File>Show software input description to display the SUT Description dialog box. c.
6. 7. Make a note of the IP address and port number. Close the dsmscm.ini file. Copy the ZDSMSCM Client File From the Host 1. From the Windows Start menu, select Run and enter the command CMD . An example response is: Microsoft Windows XP [Version 5.1.2600] (C) copyright 1985–2001 Microsoft Corp. C:\Documents and Settings\Administrator > 2. 3. Enter: cd c:\ If a DSMSCM directory does not exist, enter the following at the C:\ prompt to create it: mkdir DSMSCM 4. 5.
250 CWD command successful 10. Enter: get zdsmexe zdsm.exe. An example response is: 200 PORT command successful. 150 Opening data connection for zdsmexe (192.231.36.1,3212d) (2334 bytes). 226 Binary Transfer complete. ftp: 2334123 bytes received in 0.20 seconds 11441.78Kbytes/sec. ftp> 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. 2.
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. The Enter CNFGINFO Process Name dialog box appears with the default name $ZPHC. 140 4. Click Next to accept the default. The Setup Type dialog box appears: 5. Check that WINSOCK is selected. Click Next.
6. Click Next to accept the default. You are now prompted to enter an IP address: 7. Enter the IP address for the host system with which DSM/SCM communicates (see “Determine the Current IP Address and Port Number” (page 137)), and click Next. NOTE: If DSM/SCM is not currently configured to communicate with a host system, accept the default IP address. You can always change this value later by editing the dsmscm.ini file.
8. Enter the IP port number for the Winsock service (see “Determine the Current IP Address and Port Number” (page 137)), and click Next. NOTE: If DSM/SCM is not currently configured to communicate with a host system, accept the default IP port number. You can always change this value later by editing the dsmscm.ini file. You are now prompted to enter the host system name. 9.
10. Click No and go to “Create an Emergency Repair Disk (ERD) or Automated System Recovery (ASR) Disk ” (page 143). 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.
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. Use the OSM Service Connection or SCF for some or all the tasks. For troubleshooting information on SWAN or SWAN 2, see the SWAN Concentrator and WAN Subsystem Troubleshooting Guide. Yellow caution symbols might appear on enclosure icons and on SWANs during the firmware update.
5. Click Perform action. This message appears: 6. Click OK. The Progress list shows the status of the CLIP action. 7. Wait until all 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. The location and version of the SWAN firmware object code file for the H06.
$SYSTEM.CSSnn.C7953P00 Step 3: Initiate the Firmware Update 1. 2. 3. From the Action list, select Firmware Update. Click Add or Add all. Click Perform Action. The SWAN Firmware Update dialog box appears. 4. Leave blank the $SYSTEM.CSSnn subvolume and filename (CP7953P00) created during the most recent DSM/SCM Build/Apply, and click OK. If you have just loaded the new RVU, the SWAN firmware location should point to the correct subvolume and file version.
When the SWAN CLIPs are updated, you can then start them. See “ Step 4: Start the SWAN Concentrator and CLIPs” (page 148). 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, Chapter 4.
4> scf names adapter $zzwan.#* SCF - T9082G02 - (16OCT98) (25SEP98) - 09/08/1999 15:53:26 System \ELI Copyright Tandem Computers Incorporated 1986 - 1998 WANMgr Names ADAPTER $ZZWAN.#* ADAPTER $ZZWAN.#S00 $ZZWAN.#S01 To Check Location and Version of New SWAN CLIP Firmware At a TACL prompt, enter the VPROC command: TACL>VPROC $SYSTEM.CSSnn.C7953P00 where nn is the number specified during the Build/Apply phase of installing the H06.03 RVU: • Use the SCF STATUS SERVER $ZZWAN.#conc-name.
-> SCF ALTER ADAPTER $ZZWAN.#conc-name, KERNELCODE swan-kernel-micode-file-name By default, the SWAN firmware object file (C7953P00) resides in the $SYSTEM.CSSnn subvolume (nn is the number of the $SYSTEM.SYSnn where the new operating system image resides): SCF ALTER ADAPTER $ZZWAN.#S01, KERNELCODE $SYSTEM.CSS04.C7953P00 NOTE: The SWAN concentrators (ADAPTER object) must be in the STOPPED state for this command to work.
Glossary A7CINFO file. A configuration file distributed with OSS products that contains information on the contents of all pax (archive) files of an OSS DSV. ALLPROCESSORS paragraph A required paragraph in the CONFTEXT configuration file that contains attributes defining the HP NonStop™ operating system image for all system processors. The ALLPROCESSORS paragraph follows the optional DEFINES paragraph.
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™ operating system. DSM/SCM creates a new software revision and activates the new software on the target system. distribution subvolume (DSV) A subvolume containing program files for a particular software product along with the release version update (RVU) document (softdoc) file for that product.
primitives, routines implicitly called from native-compiled code, emulators for TNS floating-point arithmetic, and emulators for privileged-only or long-running TNS machine operations. Open System Services (OSS) An open system environment available for interactive or programmatic use with the HP NonStop operating system. Processes that run in the OSS environment usually use the OSS application program interface.
Index FCHECK utility, 40 migrating data, 40 mod-14 extent boundary., 40 partitioned unstructured files, 40 Symbols $SYSTEM.ZTCPIP, 103 $SYSTEM.
NSE-P processor type, 73 NSKCOM, 70 O OSS EasySetup, 45, 105 large files, 42 Root Name Server $ZPNS, 77 Version 1 filesets, 44 P Pcleanup utility, 102 Planner Interface, changing profile information, 78 PORTCONF file, 104 Post-installation configuring OSS, 105 configuring RDF, 106 configuring SMF, 106 updating TCP/IP configuration files, 103 Preemptable object code, 56 PREVIEW mode, 92 Processor types NSE-A, 73 NSE-P, 73 Profiles, target, changing information, 78 PROTOCOL file configuration file location,
reactivating previous software revision, 113 running, 89, 124 ZPHITI canceling a Build/Apply request, 88, 137 starting, 108 157
