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-96
set-user-ID program
set-user-ID program. In the Open System Services (OSS) environment, a program file that
has the
S_ISUID bit set in its file mode.
shared memory. An interprocess communication mechanism that allows two or more
processes to share a given region of memory.
Shared Millicode Library. An intrinsic library containing privileged or TNS-derived millicode
routines used by many native-compiled programs and by emulated TNS programs.
This library includes efficient string-move operations, TNS floating-point emulation, and
various privileged-only operations. These routines are mode independent. They
comply with native calling conventions but can be directly invoked from any mode
without changing execution modes.
shared run-time library (SRL). A collection of procedures whose code and data can be
loaded and executed only at a specific assigned virtual memory address (the same
address in all processes). SRLs use direct addressing and do not have run-time
resolution of links to and from the main program and other independent libraries.
Contrast with dynamic-link library (DLL)
. See also TNS shared run-time library (TNS
SRL) and TNS/R native shared run-time library (TNS/R native SRL).
shell. In the Open System Services (OSS) environment, a program that interprets
sequences of text input as commands. A shell can operate on an input stream, or it
can interactively prompt and read commands from a terminal.
shielded twisted pair (STP). A transmission medium consisting of two twisted conductors
with a foil or braid shield. Contrast with unshielded twisted pair (UTP)
.
shutdown file. A file invoked by the local operator or by another shutdown file that contains
commands to shut down system devices, communications lines, and system and
application software. Contrast with startup file
.
SID. See system image disk (SID) or source ServerNet ID (SID).
signal. The method by which an environment notifies a process of an event. Signals are
used to notify a process when an error that is not related to input or output has
occurred. See also Open System Services (OSS) signal
.
signal delivery. The time when Open System Services (OSS) takes the action appropriate
for a specific process and a specific signal.
signal generation. The time when an event occurs that causes a signal for a process.
signal handler. A function or procedure that is executed when a specific signal is delivered
to a specific process.
Signaling System Number 7 (SS7). The protocol used in public networks to establish
connections between switches.