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-67
NSR-E processor
NSR-E processor. See HP NonStop™ System RISC Model E processor (NSR-E
processor).
NSR-G processor. See HP NonStop™ System RISC Model G processor (NSR-G
processor).
NSR-T processor. See HP NonStop™ System RISC Model T processor (NSR-T
processor).
NSR-V processor. See HP NonStop™ System RISC Model V processor (NSR-V
processor).
NSR-W processor. See HP NonStop™ System RISC Model W processor (NSR-W
processor).
NSR-X processor. See HP NonStop™ System RISC Model X processor (NSR-X
processor).
NSR-Y processor. See HP NonStop™ System RISC Model Y processor (NSR-Y
processor).
null object type. A placeholder object type for the Subsystem Control Facility (SCF)
NAMES and VERSION commands, which do not require explicit specification of a
particular object type.
null string. In C and C++ programs, a character string that begins with a null character.
This term is synonymous with
empty string.
OBEY file. See command file.
object. One or more of the devices, lines, processes, and files in a subsystem; any entity
subject to independent reference or control by one or more subsystems. In the
Subsystem Control Facility (SCF), each object has an object type
and an object name.
object-code library. Synonym for library.
object code file. A file containing compiled machine instructions for one or more routines.
This file can be an executable loadfile for a program or library or a not-yet-executable
linkfile for some program module. On other systems, an object code file is also known
as a
binary or as an executable.
object name. A unique name for a Subsystem Control Facility (SCF) object within a
subsystem.
object-name template. A name that stands for more than one Subsystem Control Facility
(SCF) object. Such a name includes one or more wild-card characters, such as *
(asterisk) and ? (question mark). See also wild-card character
.