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-27
dynamic-link library (DLL)
gathered from a server through the process of discovery. Contrast with static
information.
dynamic-link library (DLL). A collection of procedures whose code and data can be loaded
and executed at any virtual memory address, with run-time resolution of links to and
from the main program and other independent libraries. The same DLL can be used by
more than one process. Each process gets its own copy of DLL static data. Contrast
with shared run-time library (SRL)
. See also TNS/R library.
dynamic loading. Loading and opening dynamic-link libraries under programmatic control
after the program is loaded and execution has begun.
dynamic process configuration. Using Subsystem Control Facility (SCF) to configure a
generic process to always start in a designated primary processor (that is, to be fault
tolerant).
dynamic shared object (DSO). See dynamic-link library (DLL).
Dynamic System Configuration (DSC). A utility used in D-series and earlier release
version updates (RVUs) to make online changes to the configuration of devices and
controllers. Its interactive utility is called the Configuration Utility Program (COUP). In
G-series RVUs, similar functions are performed by Subsystem Control Facility (SCF).
E4SA. See Ethernet 4 ServerNet adapter (E4SA).
earth ground. The connection of the electrical-grounding conductors to a dependable, low-
resistance contact with the soil.
earth-grounding electrode. An electrically conductive rod that is driven into soil, thus
providing an earth-ground connection point for the electrical ground wiring in a building.
A vertical steel column of a building, with its base sunk into soil, can also serve as an
earth-grounding electrode.
earth-grounding electrode system. A grounding network created by bonding together the
grounding means in a building (for example, underground metal water pipes, structural
steel, and ground rods into the earth) and bonding them to the switchgear at the
facility’s main electrical service entrance.
ECL. See emitter-coupled logic (ECL).
ECL plug-in card (PIC). See emitter-coupled logic (ECL) plug-in card (PIC).
ECL ServerNet cable. See emitter-coupled logic (ECL) ServerNet cable.
EDIT file. In the Guardian file system, an unstructured file with file code 101. An EDIT file
can be processed by either the EDIT or PS Text Edit (TEDIT) editor. An EDIT file
typically contains source program or script code, documentation, or program output.
Open System Services (OSS) functions can open an EDIT file only for reading.