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-74
persistence manager process
persistence manager process. The $ZPM process that is started and managed by the
$ZCNF configuration utility process and that starts generic processes in G-series
release version updates (RVUs) and manages their persistence.
persistent configuration. A configuration that remains the same from one system load to
another.
persistent process. A process that must always be either waiting, ready, or executing.
Persistent processes are usually controlled by a monitor process that checks on the
status of persistent processes and restarts them if necessary.
phase-loss detector/contactor (PDC). Equipment used to detect the interruption (for 50
milliseconds or longer) or the complete loss of one or more phases of power to
computer equipment. Upon detection of a phase dropout, the contactor shuts down all
input phases to the system equipment, thereby allowing smooth system shutdown and
recovery.
physical interface (PIF). The hardware components that connect a system node to a
network.
physical link interfaces. Communications standards defined by standards organizations.
The following physical link interfaces are supported for the ServerNet wide area
network (SWAN) concentrator: RS-232, RS-442, RS-449, V.35, and X.21.
Physical view. One of several views of a server available in the view pane of the
Management window of the OSM Service Connection, TSM Service Application, and
OSM and TSM Low-Level Link. A Physical view of a server is a view of all the
enclosures and is intended to represent the actual floor plan at the site. A Physical
view of an enclosure is a visual representation of the physical placement of supported
resources inside the enclosure. See also Connection view
.
PIB. See power interface board (PIB).
PIC. See plug-in card (PIC).
PID. In the Open System Services (OSS) environment, a synonym for process ID. OSS
process ID is the preferred term in HP NonStop™ S-series system publications.
In the Guardian environment, PID is sometimes used to mean either:
•
A Guardian process identifier such as the process ID
•
The cpu, pin value that is unique to a process within a node (See HP NonStop™
Kernel user ID.)
PIF. See physical interface (PIF).
PIN. See process identification number (PIN).