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-89
searchList
searchList. For each loadfile, a list that is constructed and used by the linker and loader to
tell them which libraries to examine, and in which order, to locate symbol definitions
needed by that loadfile. The linker and loader construct the loadfile’s searchList in
accordance with that loadfile’s import control, which is set at link time by the loadfile’s
programmer. A loadfile’s searchList is unaffected by the import control of any other
loadfile.
SEB. See ServerNet expansion board (SEB).
SEB port. A connector on ServerNet expansion boards (SEBs) used for ServerNet links. An
SEB has six emitter-coupled logic (ECL)-based ServerNet ports. See also MSEB port
.
Security Manager Process (SMP). A component of the Safeguard subsystem that
manages all changes to the subject and object databases and authenticates user
logon attempts.
segment. In general, a contiguous sequence of logically related pages of virtual memory.
The pages of the segment are individually swapped in and out of physical memory as
needed. Within a loadable object file, one of the portions of the file that is mapped as
one unit into virtual memory as the file is loaded. See also code segment
and data
segment.
selectable segment. A type of logical segment formerly known as an extended data
segment. The data area for a selectable segment always begins with relative segment
4, and this area can be dynamically switched among several selectable segments by
calls to the Guardian SEGMENT_USE_ procedure. The effect is similar to a rapid
overlaying of one large data area. See also logical segment
and flat segment.
SEM. See ServerNet extender module (SEM).
semaphore. A mechanism used to provide multiple processes with access to a shared data
object.
semi-globalized. An import control characteristic of a loadfile that allows the loadfile first to
obtain symbols from its own definitions and then to obtain others as for a globalized
loadfile. See also searchList
.
sensitive command. A Subsystem Control Facility (SCF) command that can be issued only
by a user with super-group access, by the owner of the subsystem, or by a member of
the group of the owner of the subsystem. The owner of a subsystem is the user who
started that subsystem (or any user whose application ID is the same as the server
ID—the result of a PROGID option that requires super-group access). Contrast with
nonsensitive command
.
separately derived power source. A facility wiring system where power is derived from a
generator, transformer, or converter windings and there is no direct electrical
connection, including a solidly connected grounded circuit conductor (neutral), to
supply conductors originating in other facility wiring systems. Types of separately