NonStop S-Series System Expansion and Reduction Guide
Table Of Contents
- NonStop S-Series System Expansion and Reduction Guide
- What’s New in This Guide
- About This Guide
- 1 The Resizing Process
- 2 Planning System Expansion
- 3 Planning System Reduction
- 4 Reducing a System Online
- 1.Prepare the Donor System for Reduction
- 2.Record Information About the Donor System
- 3.Prepare Both ServerNet Fabrics
- 4.Inventory Enclosures to Be Removed
- 5.Prepare and Stop Devices and Processes
- 6.Ensure Devices and Processes Are Stopped
- 7.Delete Devices and Processes If Necessary
- 8.Prepare Enclosures for Removal
- 9.Finish the Reduction
- 10.Remove Other Cables From Powered-Off Enclosures
- 11.Physically Remove Enclosures From the System
- Adding Enclosures to Another System
- 5 Reducing a System Offline
- 6 Expanding a System Online
- Preparation for Online Expansion
- 1.Prepare Target System for Expansion
- 2.Record Information About Target System
- 3.Prepare Target System for Addition of Block
- 4.Save Current Target System Configuration
- 5.Copy SP Firmware File From the Target System to the System Console
- 6.Finish Gathering Information
- 7.Connect a System Console to the Enclosure
- 8.Change Group Number of Enclosure to 01
- 9.Power On Enclosure
- 10.Verify Connection Between System Console and Enclosure
- 11.Configure System Console and Enclosure
- 12.Verify SP Firmware Is Compatible
- 13.Update SP Firmware in Enclosure If Necessary
- 14.Configure Topology of Enclosure If Necessary
- 15.Power Off Enclosure
- 16.Repeat Steps 6 Through 15 If Necessary
- 17.Assemble Enclosures Into a Block
- 18.Change Group Numbers of Block to Fit Target System
- 19.Disconnect System Console From Block
- 20.Power On Added Block
- 21.Cable Block to Target System
- 22.Verify Resized Target System
- 23a.Update Firmware and Code in Block (Using TSM)
- 23b.Update Firmware and Code in Block (Using OSM)
- 24.Reload Processors in Block If Necessary
- 25.Verify Operations in Added Block
- 26.Configure CRUs in Added Block
- 7 Troubleshooting
- A Common System Operations
- Determine the Processor Type
- Determine the ServerNet Fabric Status
- Determine the Product Versions of the OSM Client Software
- Determine the Product Version of the TSM Client Software
- Move the System Console
- Stop the OSM or TSM Low-Level Link
- Start a Startup TACL Session
- Start the OSM or TSM Low-Level Link
- Start the OSM Service Connection or TSM Service Application
- B ServerNet Cabling
- C Checklists and Worksheets
- D Stopping Devices and Processes
- Safety and Compliance
- Glossary
- Index
Glossary
G-Series Common Glossary
Glossary-18
conformance document
conformance document. An implementor’s document that must accompany software
claiming conformance with a POSIX standard. The document specifies the behavior or
other aspect of the software when the standard describes a behavior or aspect as
implementation-defined.
conformance statement questionnaire (CSQ). A document that identifies how a product
implements X/Open Specifications as defined in XPG Component/Profile Definitions. A
CSQ exists for each branded product.
conforming POSIX.1 application. An application that is either an ISO/IEC-conforming
POSIX.1 application or a national-standards-body conforming POSIX.1 application.
conforming POSIX.1 application using extensions. An application that:
•
Is a conforming POSIX.1 application
•
Also uses features or facilities that are not described in ISO/IEC IS 9945-1:1990
(POSIX.1) but are consistent with the standard
•
Meets the documentation requirements of a conforming POSIX.1 application and
documents its use of nonstandard features or facilities
For example, an application using the
tdm_fork() function could be a conforming
POSIX.1 application using extensions.
CONFSAVE file. In G-series release version updates (RVUs), the automatically saved
configuration database file, which is stored on the $SYSTEM.ZSYSCONF subvolume.
See also configuration file
.
CONFTEXT file. The configuration file used as input during system generation that contains
a series of entries defining your HP NonStop™ Kernel operating system attributes. A
G-series CONFTEXT file consists of one or two paragraphs: DEFINES (optional) and
ALLPROCESSORS.
CONFxxyy file. In G-series release version updates (RVUs), a saved configuration
database file created by the Subsystem Control Facility (SCF) and stored in the
$SYSTEM.ZSYSCONF subvolume.
xxyy is the number you entered as xx.yy in the
SCF SAVE CONFIGURATION command.
(xx indicates the base version, and yy
indicates the subversion.) See also configuration file.
ConMgr. See concentrator manager process (ConMgr).
connection. (1) The path between two protocol modules that provides reliable stream
delivery service. (2) For OSM and TSM software, the logical link established between
the client software on a workstation and the server software on an HP NonStop™
S-series system after a logon sequence has been performed. The two types of logical
connections are service connections and low-level links.
Connection view. One of several views of a server available in the view pane of the
Management window of the Compaq TSM package. The Connection view is a visual