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-101
star topology
star topology. A network topology in which all nodes are connected to a central hub (HP
NonStop™ Cluster Switch). Each node has its own connection to the network, so a
break in the connection does not affect other nodes in the network. In a ServerNet
cluster, a star topology requires one cluster switch for each external fabric and can
support up to eight nodes. See also split-star topology
, tri-star topology, and layered
topology.
startup file. A file invoked by the local operator or by another startup file that contains
commands to start up system devices, communications lines, and system and
application software. Contrast with shutdown file
.
state. In Subsystem Control Facility (SCF), one of the generally defined possible conditions
of an object with respect to the management of that object. Examples of states are
DEFINED, STARTED, and STOPPED.
static information. Information that represents the set of customer-replaceable units
(CRUs) on an HP NonStop™ S-series system. Contrast with dynamic information
.
static server. In the Guardian environment, a process that runs continuously and provides a
specific service to other processes. A static server differs from a traditional UNIX
demon in that a demon actively looks for tasks to perform. A static server performs
only tasks brought to its attention by a client (requestor) process. See also demon
.
STFs. See super time factors (STFs).
storage pool. A set of physical disk volumes administered as a set of logical disk volumes.
A logical disk volume can span multiple physical disk volumes. When a logical disk
volume becomes full, more physical disk volumes can be added.
storage-pool file. A file containing a list of disk volumes to be used by an Open System
Services (OSS) fileset. As these volumes are filled, more volumes can be added to the
storage-pool file.
storage subsystem. A subsystem of the HP NonStop™ Kernel operating system that
handles configuration and management of disk and tape devices in G-series release
version updates (RVUs).
storage subsystem manager process. The generic process that starts and manages disk
and tape drives. The $ZZSTO storage subsystem manager process is started and
managed by the $ZZKRN Kernel subsystem manager process through the $ZPM
persistence manager process.
store and forward routing. A form of message routing whereby a router must receive an
entire packet or message before it can start to forward the packet or message to the
next router. Contrast with wormhole routing
.
STP. See shielded twisted pair (STP).