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-103
Subsystem Control Facility (SCF)
Each subsystem has a manager through which applications can request services by
issuing commands defined by that subsystem. See also subsystem manager
.
Subsystem Control Facility (SCF). An interactive interface for configuring, controlling, and
collecting information from a subsystem and its objects. SCF enables you to configure
and reconfigure devices, processes, and some system variables while your HP
NonStop™ S-series server is online.
Subsystem Control Point (SCP). The message router for Subsystem Control Facility
(SCF). There can be several instances of this process. Using the Subsystem
Programmatic Interface (SPI), applications send each command for a subsystem to an
instance of the SCP process, which in turn sends the command to the manager
process of the target subsystem. SCP also processes a few commands itself. It
provides security features, version compatibility, support for tracing, and support for
applications implemented as process pairs.
subsystem manager. A process that performs configuration and management functions for
a subsystem.
Subsystem Programmatic Interface (SPI). A set of procedures and associated definition
files and a standard message protocol used to define common message-based
interfaces for communication between management applications and subsystems. It
includes procedures to build and decode specially formatted messages; definition files
in Transaction Application Language (TAL), COBOL85, and HP Tandem Advanced
Command Language (TACL) for inclusion in programs, macros, and routines using the
interface procedures; and definition files in Data Definition Language (DDL) for
programmers writing their own subsystems.
subvolume. A group of related files stored on a disk. All the files have the same volume
and subvolume name, but each file has a unique file identifier.
summary report. A brief informational listing of status or configuration information provided
by the Subsystem Control Facility (SCF) STATUS or INFO command. Contrast with
detailed report
.
superblock. The part of the Open System Services (OSS) environment that contains all the
information about the current state of the OSS file system. The superblock contains
such items as the free list and the size of inodes.
super group. The group of user IDs that have 255 as the group number. This group has
special privileges; many HP utilities have commands or functions that can be executed
only by a member of the super group.
super-group user. A user who can read, write, execute, and purge most files on the
system. Super-group users have user IDs that have 255 as the group number.
super ID. On HP NonStop™ systems, a privileged user who can read, write, execute, and
purge all files on the system. The super ID is usually a member of a system-supervisor
group.