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-17
CONFIG file
CONFIG file. In G-series release version updates (RVUs), the current system configuration
database file, which is stored on the $SYSTEM. ZSYSCONF subvolume. See also
configuration file
.
configuration. (1) The arrangement of enclosures, system components, and peripheral
devices into a working unit. (2) The definition or alteration of characteristics of an
object.
configuration file. In G-series release version updates (RVUs), one of the following files:
CONFBASE, CONFIG, one or more saved configuration files named CONF
xxyy, and
CONFSAVE
. See also system configuration database. In RVUs prior to the G-series,
the configuration file is either the OSCONFIG file used by the Configuration Utility
Program (COUP) or the CONFTEXT file used during system generation.
configuration planner. The person who manages system configuration changes and
software configuration changes. This person modifies the system configuration
database for system configuration changes and creates a new operating system image
for software configuration changes. See also planner
.
configuration revision. A planner-defined set of software products and related
configuration information that the Distributed Systems Management/Software
Configuration Manager (DSM/SCM) can activate on a target system. Multiple
configuration revisions might exist on a target system. A configuration revision is made
up of the product versions named in its software revision list, its HP NonStop™ Kernel
operating system image, and the relevant profile items, such as the location of the
target subvolumes on the target system. It is created by a Build request and is included
in the activation package sent to the target system.
configuration tag. Each configuration tag identifies and configures the topology of a cluster
switch and its unique position within the topology. The configuration tag defines which
ServerNet node numbers the cluster switch supports.
configuration utility process. The $ZCNF process that is the access process for the
CONFIG file and starts and maintains the $ZPM persistence manager process.
Configuration Utility Program (COUP). A utility used in D-series and earlier release
version updates (RVUs) to make online changes to the configuration of devices and
controllers. COUP is part of the Dynamic System Configuration (DSC) facility. In
G-series RVUs, similar functions are performed by the Subsystem Control Facility
(SCF).
configured object. A Subsystem Control Facility (SCF) object that exists at the time a
subsystem completes its initialization process, or an SCF object that is brought into
existence by a command issued through a subsystem management interface.
CONFLIST file. The output file produced during system generation, including error and
warning messages.
conformance. Meeting the requirements of a specific standard.