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-68
object type
object type. The category of Subsystem Control Facility (SCF) objects to which a specific
SCF object belongs. For example, a specific disk has the object type DISK, and a
specific terminal can have the object type SU. Each subsystem has a set of object
types for the objects it manages.
obsolescent. An indication that a feature or facility exists for compatibility with older
versions or drafts of a standard. Obsolescent features or facilities should not be used
because they might be removed from future versions of a standard and therefore might
not be portable.
offline. (1) Used to describe tasks that are performed outside of the control of an application
or computer system. (2) Used to describe tasks that require system resources to be
shut down. Contrast with online
.
offline change. Any change that requires system resources to be shut down. Offline
changes are usually performed during a planned outage. Contrast with online change
.
offline configuration. Configuration performed offline by SYSGENR. If necessary, you edit
the CONFTEXT configuration file to create a new configuration and then run the
Distributed Systems Management/Software Configuration Manager (DSM/SCM) (which
in turn runs SYSGENR) to generate a system image for the new configuration.
ohm. The standard unit for measuring resistance.
online. Used to describe tasks that can be performed while the HP NonStop™ Kernel
operating system and system utilities are operational. Contrast with offline
.
online change. Any change that can be performed while an application or its system
resources are operational. In some situations, online changes might temporarily affect
subsystem and application availability. For example, altering the characteristics of a
communications line might temporarily affect applications that use the communications
line. Contrast with offline change
.
Online Support Center (OSC). The group of support specialists within the HP Global
Customer Support Center (GCSC) who respond to telephone calls regarding system
problems and diagnose malfunctioning systems using remote diagnostic links.
open file. In the Open System Services (OSS) file system, a file with a file descriptor.
open file description. In the Open System Services (OSS) file system, a data structure
within an HP NonStop™ node that contains information about the access of a process
or of a group of processes to a file. An open file description records such attributes as
the file offset, file status, and file access modes. An open file description is associated
with only one open file but can be associated with one or more file descriptors.
open migration. In the Open System Services (OSS) file system, the set of events and
outcomes that occur when an open file description is inherited by a child process in a
different processor than its parent process. Contrast with open propagation
.