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-79
private dynamic-link library (private DLL)
operating system. The primary processor is the processor that has direct control over
the SAC. Contrast with backup processor
.
private dynamic-link library (private DLL). See ordinary dynamic-link library (ordinary
DLL).
problem incident report. A type of incident report that reports a problem in the server. A
problem incident report is generated when changes occur on the server that could
directly affect the availability of system resources.
procedure entry-point (PEP) table. A table in a TNS object file that contains the entry point
addresses for each procedure and is located in the first page of each code segment.
process. (1) A program that has been submitted to the operating system for execution, or a
program that is currently running in the computer. (2) An address space, a single
thread of control that executes within that address space, and the system resources
required by that thread of control.
process group. In the Open System Services (OSS) environment, a set of processes that
can signal associated processes. Each process in a node is a member of a process
group. The process group has a process group ID. A new process becomes a member
of the process group of its creator.
process group ID. In the Open System Services (OSS) environment, the unique identifier
representing a process group during its lifetime.
process group leader. In the Open System Services (OSS) environment, the process that
has the process group ID of its process group as its OSS process ID.
process group lifetime. In the Open System Services (OSS) environment, the period that
begins when a process group is created and ends when the lifetime of the last
remaining process of the group ends.
process ID. In the Guardian environment, the content of a 4-integer array that uniquely
identifies a process during the lifetime of the process. See also PID
.
process identification number (PIN). A number that uniquely identifies a process running
in a processor. The same number can exist in other processors in the same system.
See also process ID
.
process image file. On a UNIX system, an executable object file. In some Guardian
product externals and end-user publications, an executable object file is referred to as
a
program file. See also object code file.
process lifetime. The period that begins when an Open System Services (OSS) process is
created and ends when its OSS process ID is returned to the system for reuse.
PROCESS object type. In a subsystem, the object type for the subsystem manager
process itself or any generic process.