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-20
core file
core file. See saveabend file.
correctable memory error (CME). An error caused by incorrect data at a particular
memory location. The cause of the error is such that the error is automatically
corrected by the system. Contrast with uncorrectable memory error (UCME)
.
COUP. See Configuration Utility Program (COUP).
CPU. See central processing unit (CPU).
cpu, pin. In the Guardian environment, a number pair that uniquely identifies a process
during the lifetime of the process, consisting of the processor (CPU) number and the
process identification number (PIN). See also PID
.
CRC. See cyclic redundancy check (CRC).
creation version serial number (CRVSN). In the Open System Services (OSS)
environment, a number assigned by a disk process when a file is created. The CRVSN
is used by the disk process and the OSS name server process to verify that the correct
file is accessed. The CRVSN is stored in the catalog entry for an OSS regular file and
is passed to the disk process when a Data Definition Language (DDL) request that
involves the file is made.
critical load. Equipment that must have an uninterruptible power input to prevent damage
to the equipment or the facility or prevent injury to personnel.
CRPC. See computer-room power center (CRPC).
CRU. See customer-replaceable unit (CRU).
CRVSN. See creation version serial number (CRVSN).
CSQ. See conformance statement questionnaire (CSQ).
current. The movement of electrons caused by potential difference between two
electromotive charge forces.
current configuration file. See configuration file.
current working directory. In the Open System Services (OSS) environment, the directory
used in pathname resolution of relative pathnames. A process always has a current
working directory. See also working directory
.
CUSTFILE. An EDIT file included on every site update tape (SUT) as
$SYSTEM.A
nnnnnn.CUSTFILE, where nnnnnn is the system serial number of the
target system. The CUSTFILE contains information on the software products on the
SUT, their related files, and the destination and use of each file. HP customizes
information in the CUSTFILE for each customer’s system.
customer engineer (CE). See service provider.