H06.14 Software Installation and Upgrade Guide HP Part Number: 545778-003 Published: March 2011 Edition: H06.
© Copyright 2008, 2011 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.
Contents About This Document...................................................................................10 Supported Release Version Updates (RVUs)................................................................................10 Intended Audience..................................................................................................................10 New and Changed Information in This Edition............................................................................
3 H06.14 Installation, Migration, and Fallback Considerations..........................38 H06.03.................................................................................................................................38 Kernel-Managed Swap File (KMSF)......................................................................................38 IOAM and Migrating Existing Data to an Enterprise Storage System (ESS).................................38 OSS Database Files........................................
Fallback with Standard Security (Safeguard Not Installed)..................................................51 Compiler Default Change for Object Code Generation...........................................................52 COBOL H06.08 and Later Fallback .....................................................................................52 C H06.08 and Later Fallback..............................................................................................52 H06.09........................................
Verify Tape Drives (If Necessary)..........................................................................................67 Check the Status of the Spooler Collector..............................................................................67 Check for Sufficient Swap File Space....................................................................................67 Install Node Interoperability SPRs..............................................................................................
Using OSS Unautomated Configuration and Startup........................................................103 Using OSS EasySetup (T0585)......................................................................................103 Configure SMF (Optional).................................................................................................103 Configure the Remote Database Facility (RDF) .....................................................................103 Configure the WAN Manager....................
Print Operator Instructions From the Target Interface (ZPHITI).......................................................121 Run ZPHIRNM......................................................................................................................122 If Running INSTALL^TEMPLATES Is Required.............................................................................122 If a System Load Is Required...................................................................................................
Tables 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Tasks and Tools for Backing Out to the Previous SYSnn .........................................................21 Maintenance Entity (ME) Firmware.....................................................................................24 Maintenance Entity (ME) FPGA..........................................................................................26 Minimum Required Firmware Versions for NS14000 and NS16000 Systems............................
About This Document This guide describes: • Upgrading the initial H06.14 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.14.00 RVU and all subsequent H06.14.nn RVURs unless otherwise noted. Exceptions are called out in the text.
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.14 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.
exit(-1); } Bold Text Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.
• The following planning guides provide information for planning and configuring the installation of NonStop NS-series servers: ◦ NonStop NS1000 Planning Guide ◦ NonStop NS1200 Planning Guide ◦ NonStop NS14000-Series Planning Guide ◦ NonStop NS16000-Series Planning Guide ◦ NonStop NS-Series Carrier Grade Server Manual • The NonStop Operations Guide provides information for operating and maintaining the NonStop NS-series server.
1 Overview of Installing the H06.14 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.
Systems” (page 29). For detailed information on updating firmware on an NSVA system, see the OSM Service Connection User’s Guide. • 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. Beginning with the H06.14 RVU, RCVDUMP creates a smaller extracted dump file in addition to the full dump. This smaller dump requires less time to transfer to analysts.
DSM/SCM tasks, you must download the DSM/SCM client and install it separately (it is not included on the installer DVD). If you are migrating a G-series legacy system console to use OSM, certain client-side system requirements must be met. See the NonStop System Console Installer Guide and the OSM Migration and Configuration Guide for PC system requirements and information on migrating to OSM.
SIM, see the NonStop System Console Installer Guide. To enable SSL, see the OSM Migration and Configuration Guide. • An advanced firmware update feature that simplifies firmware update procedures.
For more information on OSM client applications, see the OSM Migration and Configuration Guide or the online help available from within each application. To upgrade an existing system console to the latest console software, see the NonStop System Console Installer Guide. Using DSM/SCM With the H06.14 RVU • “ DSM/SCM and the H06.
WARNING! If an H06.12 or later host system is used to perform DSM/SCM builds for a target system that is running a release prior to H06.12, you must install the appropriate T0431 (OSBUILD) SPR for that target system before performing the build. If this is not done, then the DSM/SCM Sysgen (OSBUILD) will fail. The build will complete successfully if it is being done for an H06.12 or later system. The appropriate T0431 SPRs are: SPR Target System RVU T0431H01^AAK H06.10 and H06.11 T0431H01^AAH H06.
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.
IMPORTANT: Guide. For NonStop NS2000 systems, see the J06.nn Software Installation and Upgrade System SYSTEM_PROCESSOR_TYPE NSAA systems (NS16000, NS16200, NS14000, NS14200) NSE-A NSVA systems (NS1000, NS1200, NS3000AC, NS5000) NSE-P Check the CONFTEXT file to ensure that the following entries are present.
Table 1 Tasks and Tools for Backing Out to the Previous SYSnn (continued) To Perform This Task... Use This Tool... Documented in This Chapter... 4. Load the HP NonStop operating OSM Low-Level Link system from the previous revision into the first processor. Chapter 12: “Loading the Previous RVU and Resuming Normal Operations ” 5. Reload the remaining processors.
2 Managing Microcode and Firmware for NonStop NS-Series Servers NOTE: Trained HP service providers will update the firmware when they install any field-replaceable units (FRUs). Firmware, unless otherwise noted, is considered customer-updateable. You must manage all microcode and firmware within your system properly, updating it as necessary when new versions become available. Failure to do so can result in a wide range of system problems, from intermittent faults to partial or complete system outages.
either the OSM Service connection or the Low-Level Link. The following sections describe how to update ME firmware using the OSM Service Connection: • • “Updating ME Firmware” ◦ Updating ME Firmware on a Processor Switch ◦ Updating ME Firmware on an I/O Adapter Module ◦ Updating ME Firmware on a VIO Module “Updating ME FPGA” For information on using OSM Low-Level Link to perform ME firmware updates, see the online help available within the application.
You can also check and update ME firmware using the OSM Low-Level Link. For more information, see the OSM Low-Level Link online help. Updating ME Firmware on an I/O Adapter Module (IOAM There is maintenance entity (ME) firmware on the ServerNet Switch Board object in each I/O Adapter Module of many NonStop NS-series systems. (Some NS-series systems now contain VIO modules in place of IOAMs.) NOTE: In the OSM Low-Level Link, a ServerNet Switch Board is represented as an ME object.
Table 3 Maintenance Entity (ME) FPGA Product Number Description Host FRU Disk File Name Default Location T0437A01^AAB ME firmware (see Caution below) ServerNet Switch Board (IOAM and processor switch) SAM0437 SYSnn T0789 ME firmware for IME in VIO modules (see Caution below) VIO enclosure logic board SAM0789 SYSnn CAUTION: You should not use the Multi-Resource Actions dialog (in the OSM Service Connection) to update ME FPGA simultaneously on both fabrics, or a system outage might occur.
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. The following tables list the updateable NonStop Blade Complex firmware and the recommended order for updating firmware through the guided procedure.
Table 5 Minimum Required Firmware Versions for NS14200 and Mixed NS14000/NS14200 Systems Firmware Product Module File Name Product Level Product Description Halted State Services (HSS) Firmware HSSFWAAH T0287H01^AAH Contains HSS Main firmware. DISKBOOT firmware DSKFIRMW T2773H01* Diskboot is used during a system load of a NonStop NS-series server. PAL/SAL Firmware IPFFWAAH T0287H01^AAH A firmware library based on the Intel Itanium architecture.
Table 6 Minimum Required Firmware Versions for NS16200 and Mixed NS16000/NS16200 Systems (continued) Firmware Product Module File Name Product Level Product Description Baseboard Management Controller (BMC) M0661 Firmware M0661AAA T0661AAB BMC firmware is used for board and module maintenance. Unlike the other Blade Element firmware, BMC firmware updates require a reset of the BMC only in the updated Blade Element.
ISP1040, PAL/SAL, DISKBOOT, Halted State Services, and Baseboard Management Controller Firmware) resides on the flash memory devices. These flash or firmware images as defined and used in the Blade Complex Firmware Update guided procedure are: • The shadow image, which is the firmware image in the local flash memory that is not currently running. This firmware image is designed to be used only when the the current running image is unavailable or during a firmware update.
NonStop Blade Complex Firmware Update for Migrations From H06.03 or H06.04 to H06.14 CAUTION: Do not power cycle any NonStop Blade Element until the firmware update is complete. If you interrupt or stop the procedure before the firmware update has completed, the NonStop Blade Element firmware will be left in an incomplete and inconsistent state. Also, if there is an interruption during the firmware update, do not reset or power cycle the NonStop Blade Elements.
1) 2) 3) Using the OSM Service Connection and the Blade Complex Firmware Update guided procedure, complete the dialog boxes and update the shadow firmware on each NonStop Blade Element. 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 NO. Repeat steps 1 and 2 for the other NonStop Blade Complexes.
Managing ServerNet Adapter Firmware This manual covers only the ServerNet adapters supported in I/O adapter modules (IOAMS): • Fibre Channel ServerNet adapter (FCSA) • Gigabit Ethernet 4-port ServerNet adapter (G4SA) To update firmware for ServerNet adapters connected to legacy IOMF2 CRUs, see the latest G-series Software Installation and Upgrade Guide.
• ◦ RAM firmware: Operational firmware is downloaded to the FCSA when you issue the first START DISK command to the first disk drive in the fibre-channel loop. ◦ Use the OSM Service Connection to check the FCSA’s firmware version and update the firmware, if needed. If the Compare State shows Down-rev, update the firmware. The following example shows that the firmware is at an earlier version and needs to be updated: G4SA.
Table 8 H-Series ServerNet Adapters Product Number Description Host FRU Disk File Name Default Location Tool Related Information T0630G06^AAN Fibre Channel FCSA ServerNet Adapter (FCSA) Flash firmware I0630 SYSnn subvolume OSM SC or SCF Fibre Channel ServerNet Adapter (FCSA) Installation and Support Guide T0612G06 ^AAB FCSA Flash FCSA Boot firmware C0612R00 SYSnn subvolume OSM SC or SCF Fibre Channel ServerNet Adapter (FCSA) Installation and Support Guide T0612G06 ^ AAB G4SA firmware C0612
Table 8 H-Series ServerNet Adapters (continued) Product Number Description Host FRU Disk File Name Related Information Default Location Tool T0612G06 ^ AAB FCSA Flash VIO enclosure Boot firmware for VIO C0612R00 SYSnn subvolume OSM SC or SCF Fibre Channel ServerNet Adapter (FCSA) Installation and Support Guide and hardware installation manuals for the NS1000, NS1200, and NS14000–series servers T0612G06 ^AAB G4SA firmware for VIO C0612R00 SYSnn subvolume OSM SC or SCF Gigabit Ethernet 4–Port
Table 10 Updateable Firmware for the NonStop ServerNet Switch Product Number Description Host CRU/FRU Disk File Name Default Location Tool Related Information T2790 AAB Cluster switch 6780 firmware (logic ServerNet board Switch configuration) M2789 SYSnn subvolume SCF; OSM SC ServerNet Cluster 6780 Operations Guide T2789 AAD Cluster switch firmware (logic board: router-2 firmware*) 6780 ServerNet Switch (Router-2 ASIC*) C2790 SYSnn subvolume SCF; OSM SC ServerNet Cluster 6780 Operations Guid
3 H06.14 Installation, Migration, and Fallback Considerations See the Readme file and the appropriate softdocs for the latest information on any migration or configuration steps. Considerations in this chapter are categorized according to the RVU at which they were introduced. H06.03 Kernel-Managed Swap File (KMSF) NonStop NS-series servers require more swap space than do NonStop S-series servers. The default is 512 megabytes for each processor.
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.
PSTATE (T0705H01) and WHOHAS (T0706H01) PSTATE and WHOHAS are two tools that are owned and supported by the Global Mission Critical Solution Center (GMCSC). As of H06.03 and G06.26, these two tools are delivered to customers on the SUT. • PSTATE provides a snapshot of the status of a running process. It provides everything that TACL STATUS, DETAIL does plus information about all files open by the process and what I/Os are outstanding. • WHOHAS provides a list of processes that have open files.
Visual Inspect: Restart $IMON Required If you use Visual Inspect, you must restart the Inspect Monitor process ($IMON) every time you restart the system. C/C++ Default Floating-Point Type Change Beginning in the H-series RVUs, the default floating-point format used by the C/C++ compiler is changed. In G-series, the default is Tandem floating-point format; on H-Series, the default IEEE format.
ServerNet Cluster Starting in H06.05, the HP NonStop ServerNet Switch (model 6780) can support the long-distance option in a three-zone configuration of the layered topology. Before this RVU, the long-distance option was restricted to a two-zone configuration. To use the ServerNet cluster long-distance option in a three-zone configuration, you must install the H06.05 or later H-series RVU or the T0502H01^AAP or later SPR. HP recommends upgrading the NonStop NS-series servers to the H06.
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. TNS/R Compilers and Tools on H-Series Systems Use One Platform for G-Series and H-Series Development Beginning with H06.05, the G-series TNS/R compilers and development tools are supported in H-series RVUs.
TNS/R SRLs Consolidated Into a Single T-Number The TNS/R cross compiler SRLs are consolidated into a single T-number, T8888 (named “TNS/R cross compilers SRLs”). This T-number contains all of the runtime libraries and object files that make up the cross compiler environment.
H06.06 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.
DSAP/DCOM Migration The DSAPDDL file is changed in the product revision of DSAP/DCOM delivered in the H06.06 and later RVUs (T9543H01^ABH), resulting in changes to the work file layout. You must use the DSAPDDL file distributed with T9543H01^ABH when running ENFORM queries on the work 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.
Guardian applications that use file attributes such as file format and maximum size are likely to be affected. These programs might fail when unexpected values are returned (such as Format 2 if only Format 1 is expected). 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.
Safeguard Password Encryption The H03 and later versions of Safeguard and Standard Security improve the cryptology of the user passwords in the NonStop server environments. If PASSWORD-ALGORITHM is DES or PASSWORD-ENCRYPT is OFF, the password (DES-encrypted or in clear text, respectively) is written to both the existing L/USERID and the new L/USERAX files. This approach allows for direct fallback to prior versions of Safeguard and Standard Security.
This is especially important for the system administrator. After installing the previous version of Safeguard and Standard Security: 1. 2. 3. 4. Before starting Safeguard, the system administrator must log on with the old super ID password. The old password is the one used before the algorithm was changed to HMAC256. Start Safeguard. The system administrator must set a grace period for users to change their expired passwords.
Compiler Minimum SPR Level 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.09 RVU, the Profile Merge Utility (T0747) and Code Cover Utility (T0746) are included on the SUT and on the cross-compiler CD. Previously, the Profile Merge Utility was delivered only on the SUT.
Fallback To fall back, you must install the previous SPRs for the OSS products and for DP2. In addition, in either of these cases, you must run fsck on the fileset to downgrade the fileset to Version 2: • If the fsck utility has been run on a fileset to upgrade to Version 3 filesets • If the fileset was created on a system running an H06.08 or later H-series RVU When the fileset is downgraded to Version 2, any optional ACLs associated with the files in the fileset are lost.
3. 4. Log on using the 8 character password. Use the PWCONFIG utility to change the PASSWORD-MINIMUM-LENGTH attribute to a value less than 8. Once these steps are completed, users whose password length is less than or equal to 8 bytes will be able to log on. Users whose password length exceeded 8 bytes before fallback will be unable to log on; the system administrator must change their passwords to have a length less than or equal to 8 bytes.
devices. Instead, the SNMP read Access Community password is required for monitoring the Maintenance Switch, and both the SNMP Read Access Community and SNMP Write Access Community passwords are required to start monitoring the UPS. These passwords are established the administrator during initial configuration of the device. The default password for SNMP Read Access Community is “public”; The default password for SNMP Write Access Community is “private.
For more information on the password quality enhancements, see the Password Quality Enhancements support note. Migration There are no migration considerations specific to the quality password feature. However, a mitigation procedure is available for handling any unexpected failures that might occur during migration. This procedure is described under “Migration in a Safeguard Environment” (page 48). Fallback Embedded spaces in passwords are not supported in pre-H06.09 RVUs.
NOTE: All NonStop SQL/MX objects must reside on volumes audited by TMF. NonStop SQL/MX program files do not need to reside on audited volumes. Before installing NonStop SQL/MX, review the instructions for preinstalling and installing NonStop SQL/MX provided in the SQL/MX Installation and Management Guide. Pathway/iTS 1.1 Pathway iTS/1.1, introduced in the H06.
NonStop Secure Shell Server NonStop Secure Shell (SSH) Server was introduced in the H06.11 RVU. NonStop SSH Server provides secure communication between the MR-Win6530 terminal emulator (which replaces OutsideView) and the NonStop server. Migrating to SSH Server NonStop SSH Server is an optional product, and must be set up for use with MR-Win6530. In terms of network management, NonStop SSH Server uses port 22, so that port must be enabled for NonStop SSH Server to work. H06.
H06.14 Minimum SPR Levels Required for Clustering Software In order to add a BladeSystem node to an existing ServerNet cluster having both S-series and Modular nodes, the following minimum SPR levels are required for ServerNet Cluster Monitor (T0294) and ServerNet Cluster Fabric Manager (T0502): Node Minimum Requirement for T0294 Minimum Requirement for T0502 S-Series T0294AAX T0502AAX (only the PM module (that is, the ZSMNSCF file) has changed) Modular and BladeSystem T0294AAW T0502AAW TS/MP 2.
4 Upgrade Checklist Use the checklist in Table 11 as you perform the tasks required to upgrade to the H06.14 RVU and the checklist in Table 12 (page 59) to record the information needed when performing these tasks. Table 13 (page 60) lists SPRs that should be installed before upgrading to H06.14. You might have to update the service processor (SP) firmware on NonStop S-series systems for IOMF2 PMF customer-replaceable units (CRUs). H06.14 Upgrade Checklist Table 11 H06.
Table 11 H06.14 Upgrade Checklist (continued) Task Description Reference Done? 20. Configure WANMGR (if necessary). “Configure the WAN Manager” (page 103) 21. Update SWAN concentrator CLIP firmware (if necessary). SWAN Concentrator Installation and Support Guide or SWAN 2 Concentrator Installation and Support Guide 22. Start system and application software. “Start User and System Applications” (page 98) 23. Configure OSS (if necessary). “OSS Large Files” (page 45) 24.
Table 12 H06.
5 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.14 RVU. At a TACL prompt, issue the status command to determine the current SYSnn subvolume.
• “Verify Tape Drives (If Necessary)” (page 67) • “Check the Status of the Spooler Collector” (page 67) • “Check for Sufficient Swap File Space” (page 67) 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.
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.
Verify Critical System Processes 1. From a TACL prompt, log on to the system using the super ID (255,255). Enter the LISTDEV command: > 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.$ADAUD LDev Primary Backup Mirror 151 *STARTED STARTED MirrorBackup *STARTED STORAGE - Status DISK \ATLAS.$ADBIT LDev Primary Backup Mirror 150 *STARTED STARTED MirrorBackup *STARTED STORAGE - Status DISK \ATLAS.
KMSF swap files need to be larger than in G-series RVUs. The best practice is to monitor swap file usage. See the Kernel-Managed Swap Facility (KMSF) Manual for information on configuring swap file space. To check the size of the configured swap files for each processor: 1. At a TACL prompt, start NSKCOM: $SYSTEM STARTUP 5> nskcom NSKCOM - T5838H01 BASE (01OCT04) - Apr 15 2005 Copyright 1995 Compaq Computer Corporation $SYSTEM.SYSTEM.ZSYSCFG KMS.SWAPFILE = 0 $SYSTEM.ZSYSSWAP.SWAP00 KMS.
Install Node Interoperability SPRs Node interoperability is the ability of the nodes (systems) in a network of NonStop operating system nodes to communicate and interact with each other. For details on maintaining interoperability between NonStop S-series and NonStop K-series systems, see the Interactive Upgrade Guide 2.
Table 15 Interoperability SPRs for NonStop BladeSystems and NonStop S-Series Systems (continued) Minimum SPR Product Name Description Introduced in this RVU T9621 ABB Binder Required to recognize OCA region G06.27 T9674 AAM PDTSHARE Required to recognize OCA region G06.27 T9617 AAY VPROC Required to recognize 800 files G06.27 T9276 AAW Axcel Required to recognize OCA region G06.
6 Installing a SUT for the H06.14 RVU Installing a new RVU or a SUT involves these DSM/SCM tasks: 1. 2. 3. “Receive New Software Into the Archive” (page 71) “Create a New Software Revision” (page 75) “Build and Apply the New Software Revision” (page 78) Alerts for Installing a SUT Do not use this procedure to upgrade more than one 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.
6. 7. Under Software name, select Provided by planner and enter a name for the revision. 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.
• 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: 74 Installing a SUT for the H06.
13. When the request is finished, close the Status and Requests windows. 14. Update the Software in Archive dialog box to show the newly received SUT. Select Window>Refresh. The new SUT appears in the window. 15. Keep the Planner Interface open for the next task. Create a New Software Revision When you create a new software revision, DSM/SCM selects the products in the SUT that are licensed for your site and replaces any previous versions of the products.
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.
6. Click Continue when the Confirmation message appears: Note that if there are any discrepancies between the set of products included in the previous configuration and the set in your new configuration, a warning message appears listing any products missing in the current configuration that were present in the previous configuration. (These products are removed from the system by DSM/SCM during the Build/Apply of the new configuration.
7. Keep the Planner Interface open for the next task. Build and Apply the New Software Revision The Build process creates an activation package containing all the products listed in the new software revision. To avoid disrupting other system activity, schedule the Build to run at night and the Apply to run immediately after the Build. See the DSM/SCM User’s Guide for information about scheduling the Build/Apply to run at different times. To build and apply the new software revision: 1.
2. 3. Under Perform steps, select Build, apply & process snapshot. In the Activation SYSnn: box, enter a unique number to create a new SYSnn subvolume. The value nn must be a two-digit octal number in the range%00...%77. You can issue a FILEINFO command at a TACL prompt to view the SYSnn subvolumes that are currently on your system. > fileinfo $system.*.osimage 4. 5. 6. Make a note of the new SYSnn.
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. 80 STATE ACTIVE FLAGS 3 , CPU 1 In the Build/Apply Request dialog box, click OK. Installing a SUT for the H06.14 RVU PRI 154 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: • 82 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.14 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.
7 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.
• DNSHOSTS • DNSLOCAL • DNSREV • DNREVBAK • HOSTS • NETWORKS • PORTCONF • PROTOCOL • RESCONF • SERVICES • SMTPCONF The file names of NonStop TCP/IPv6 that reside on the SUT are: • ztcpip.smplhost • ztcpip.smplprot • ztcpip.smplnetw • ztcpip.smplport • ztcpip.smplresc • ztcpip.smplserv Stop Applications Before running ZPHIRNM: 1. Stop DSM/SCM if it is still running. For example: > VOLUME $dsmscm_vol.
1. 2. Use the SPOOLCOM;COLLECT $collector-process, LISTOPENS command to identify processes that currently have jobs open. Use the SPOOLCOM;JOB (STATE PRINT) command to determine which jobs are currently printing. Take the appropriate action to ensure that these jobs either terminate when finished or are stopped. After receiving the SPOOLER DRAIN command, the supervisor stops accepting jobs for collection or printing (new opens are rejected with a file-system error 66—device downed).
TSVs processed in old config (obsolete) .... 1 Files Processed: Files Files Files Files Files Files Files Files Files Files processed in new configuration ........................... processed in new configuration only ...................... processed in old configuration only ...................... processed that are shared by new and old configuration ... processed & unchanged between new and old configuration .. processed in obsolete TSVs ...............................
DSM/SCM Utility - ZPHIRNM - T6031H01 - (11NOV2004) Copyright Hewlett Packard Development Company L.P. 1993-2004 Do you want to use a log file with this session? (Y/N): y You may use any file for logging. If you request to use a disk file that doesn't exist, it will be created as an edit file. Please enter a filename: elist00 Log file is open, Zphirnm will now begin processing. ZPHIRNM begins processing and provides status of its progress. 4.
8 Loading the H06.14 RVU This chapter describes how to perform a system load of the H06.14 RVU into the memory of each processor in a NonStop NS-series server. NOTE: For detailed information on performing a system load of a NonStop NS-series server, see Chapter 15 in the NonStop Operations Guide. By default, one $SYSTEM is already configured. You can select $SYSTEM, FCDM-Load, SCSI-Load, or an alternate system volume: • A load from $SYSTEM attempts to load the system from a disk in group, module, slot 11.
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 17 (page 92). • You can configure additional alternate system disks. To create an alternate system disk, see the NonStop NSxxxx–Series Hardware Installation Manual. Then use OSM to make the disk available in the Configuration drop-down menu in the System Load dialog box.
6. 7. Click OK when asked “Are you sure you want to do Halts?” When the Action Status box confirms that all processors have halted, close the Processor Status dialog box. While the Processors are Halted If you are upgrading from the H06.03 or H06.04 RVU, then while the processors are halted, power cycle the processors as described in step 6b under “NonStop Blade Complex Firmware Update for Migrations From H06.03 or H06.04 to H06.14” (page 31).
Two windows for startup event stream windows (CNSLS) and two startup TACL windows (CLCIs) are automatically launched. It might take a few seconds before the windows appear. NOTE: If you are using OSM Low-Level Link version T0633AAT 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.
Completing the System Load (If Necessary) Loading the processors with the CIIN file is usually automatic. However, if the operating system loaded successfully into processor 0 or processor 1, but the commands in the CIIN file do not reload all remaining processors, use the RELOAD TACL commands. You must be super ID (255,255) to load the processors. 1. From the system console, log on to the system as a super-group user (255,nnn) and enter: > RELOAD *, PRIME 2.
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 Operations Guide.
9 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.
After you run merge_whatis, the directory contains a file named whatis, containing the database. If you have previously installed OSS, a file named whatis_old is present, containing the previous version of the database. Configure Specific Products (Post-System Load) This section contains information about the configuration of various products such as OSS and SMF. See product-specific documentation for more information on installation and configuration.
>FUP >FUP >FUP >FUP >FUP DUP DUP DUP DUP DUP $SYSTEM.ZTCPIP.SMPLPROT, $SYSTEM.ZTCPIP.SMPLNETW, $SYSTEM.ZTCPIP.SMPLPORT, $SYSTEM.ZTCPIP.SMPLRESC, $SYSTEM.ZTCPIP.SMPLSERV, $SYSTEM.ZTCPIP.PROTOCOL $SYSTEM.ZTCPIP.NETWORKS $SYSTEM.ZTCPIP.PORTCONF $SYSTEM.ZTCPIP.RESCONF $SYSTEM.ZTCPIP.SERVICES Step 2: Check the PROTOCOL File (Optional) 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.
Applications use the SERVICES file to retrieve the service port numbers and service names. If you copied files as documented in Step 1, check that the last lines of the SERVICES file have an entry similar to: phiwsock 1089/tcp #DSM/SCM Planner Interface For DSM/SCM, the port number is user-definable. The setup default is 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.
NOTE: To preserve the original inetd.conf file—before using COPYOSS or PINSTALL—the following steps must be done to prevent COPYOSS or PINSTALL from overwriting the original inetd.conf file: • Save the original inetd.conf file by using the command: > mv inetd.conf smplinetd.conf • After running COPYOSS or PINSTALL, if the original inetd.conf file needs to be restored, use the command: > mv smplinetd.conf inetd.
1. 2. Configure the WAN manager as described in the WAN Subsystem Configuration and Management Manual. Update the SWAN CLIP firmware. See either the SWAN Concentrator Installation and Support Guide or the SWAN 2 Concentrator Installation and Support Guide.
10 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. NOTE: • You cannot revert a NonStop NS16200 system to the H06.11.03 RVU or to an RVU prior to H06.11.01. • You cannot revert a NonStop NS1200 system to an RVU prior to H06.12. • You cannot revert a NonStop NS14200 system to an RVU prior to H06.13.
Longer Passwords Starting with the version of Safeguard released with the H06.08 RVU, the maximum allowed password length is increased to 64 characters. This change has fallback implications when falling back to pre-H06.08 RVU, as users passwords longer than 8 characters will be unable to logon. See “Safeguard Longer Password Length” (page 51). Before Backing Out the Revision 1. Confirm that the spooler is active and not 100 percent full. a.
DSM Software Configuration Manager Main Menu ============================================================================== \ELI Prior snapshot 2002-04-14:18:03:03 Selection number: 0 ============================================================================== Choose an action by entering the selection number of an item from the list below.
============================================================================== 1 Perform/Review apply request 2 Perform backout to S/W Applied on SYS 03 on 2005-04-14:15:41 3 Review operator instructions for the last apply completed. ============================================================================== F1-Select F15-Help F16-Return SF16-Exit Ready 3. In the Selection number field, enter 2 (Perform backout to S/W), and press F1.
============================================================================== F3-Restart F4-Show messages F6-Cancel request F15-Help F16-Return SF16-Exit DSM Software Configuration Manager Backout - Processing Backout ============================================================================== \ELI Prior snapshot 2002-04-14:18:03:03 DEFAULT Last S/W applied on SYS00 on 2002-04-14:18:01 Backout 2000-04-18:11:00:39 ============================================================================== Request is b
Monitor the Backout Process 1. 2. Log on to DSM/SCM (Start>Programs>dsm_scm>DSMSCM). 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.
11 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.
without actually updating files or activating the configuration. In PREVIEW mode, ZPHIRNM indicates whether or not TMF needs to be up when running ZPHIRNM. Run ZPHIRNM 1. At a TACL prompt, enter from the DSM/SCM subvolume: > RUN ZPHIRNM $vol.SYSnn where: • $vol specifies the default current system load volume, usually $SYSTEM. • SYSnn specifies the SYSnn subvolume named previously in the backout request. For example: > RUN ZPHIRNM $system.SYS00 2. 3. 4.
12 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 a 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.
Loading the System A normal system load consists of loading the operating system from disk into the memory of processor 0 or processor 1: 1. 2. In the OSM Low-Level Link, select Start System. The System Load dialog box appears. In the System Load dialog box, select $SYSTEM or a saved configuration. a. In the SYSnn field, enter nn, which is the number of the system subvolume that contains the version of the operating system you will load. b.
1. From the system console, log on to the system as a super-group user (255,nnn) and enter: > RELOAD *, PRIME 2. To load an individual processor or processors, enter: > RELOAD nn where nn is the processor number of the processor you want to reload. If the reload is initiated successfully, this message appears in a startup TACL window on the system console screen: PROCESSOR RELOAD: nn After Coldloading the Previous RVU If you are falling back to the H06.03 or H06.
5. 6. 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. Update NonStop Blade Complex (NSBC) firmware: 1) Using the OSM Service Connection and the Blade Complex Firmware Update guided procedure, complete the dialog boxes and update the shadow firmware on each NonStop Blade Element.
Reverting to H06.05 or Later From H06.14 CAUTION: Do not power cycle any NonStop Blade Element until the firmware update is complete. If you interrupt or stop the procedure before the firmware update is completed, the NonStop Blade Element firmware will be left in an incomplete and inconsistent state. Also, if there is an interruption during the firmware update, do not reset or power cycle the NonStop Blade Elements. Instead, immediately start the procedure from the beginning.
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.
• A summary of problems corrected • A summary of known problems remaining Keep a copy of each SPRNOTE and record the status of the related SPR. For example, record whether the SPR is not applicable, is already installed, or needs to be installed. Install SPRs 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.
OSIMAGE 0 57354240 15DEC1999 9:57 255,255 NUNU 200 200 $SYSTEM.SYS01 CODE 0 OSIMAGE 3. EOF LAST MODIFIED 57393152 05APR2000 8:56 OWNER RWEP 255,255 NUNU PExt SExt 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.
1. In the Configuration Revisions dialog box, select the configuration you are updating, and click New Software Revision. The New software revision dialog box appears. 2. In the Software in Archive dialog box, select SPRs to be added to the current configuration and click Copy to. Build the New Revision After you have created a new software revision, prepare to install it on your target systems by building it into an executable form: 1.
Run ZPHIRNM During the Build/Apply phase, DSM/SCM places product files in their subvolumes with temporary (fabricated) file names so that the new files do not conflict with the file names of currently running programs. After the Build/Apply finishes, run the ZPHIRNM program on the target system to: • Rename the files that currently have actual file names with fabricated names. These files become obsolete when the new files are renamed. • 1.
-> load /keep 1/ TACLMACS NOTE: If you run the INSTALL^TEMPLATES macro with no arguments, you are prompted to provide required information. For information on the INSTALL^TEMPLATES arguments, print the usage notes: -> volume $system.zinsaids -> load /keep 1/ TACLMACS -> install^templates /out outdev/ help where outdev is the name of the desired output device. 3. Choose a location on $SYSTEM to keep updated template files: tacl>volume $system.template 4.
>$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.TEMPLATE.NEWRES,$SYSTEM.TEMPLATE.NEWNRES),"NUNU" *** INSTALL^TEMPLATES: Completed sucessfully *** If a System Load Is Required If OSM is installed and configured, use these instructions to load your RVU. Before Halting the Processors If you are falling back to the H06.03 or H06.
B Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software NOTE: • For 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.14, all newly shipped 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.
VPROC - T9617H01 - (01 OCT 2004) SYSTEM \DRP08 Date 12 MAY 2006, 18:20:13 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.14 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.14 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. 136 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 133)), 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 133)), 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. 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. See either the SWAN Concentrator Installation and Support Guide or the SWAN 2 Concentrator Installation and Support Guide.
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.
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. Interactive users of the OSS environment usually use the OSS shell for their command interpreter. Synonymous with Open System Services (OSS) environment.
Index Symbols $SYSTEM.ZTCPIP, 100 $SYSTEM.
EasySetup, 39, 103 large files, 45 Root Name Server $ZPNS, 75 Version 1 filesets, 50 Swap file space, checking , 67 SYSnn subvolumes listing, 62 System configuration file, 119 P T Pcleanup utility, 99 Planner Interface, changing profile information, 76 PORTCONF file, 101 Post-installation configuring OSS, 102 configuring RDF, 103 configuring SMF, 103 updating TCP/IP configuration files, 100 Preemptable object code, 52 PREVIEW mode, 90 Processor type in CONFTEXT file, 20 Profiles, target, changing inform
