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-73
path prefix
path prefix. In the Open System Services (OSS) environment, a pathname with an optional
final slash (
/) character that refers to a directory.
PDC. See phase-loss detector/contactor (PDC).
PDP. See power distribution panel (PDP).
PDU. See computer-room power center (CRPC) and power distribution unit (PDU).
peak load current. The maximum instantaneous load over a designated interval of time.
PEEK. A utility program that reports statistics on resource use in a processor. PEEK is used
to ensure proper allocation of memory and processes in a system after system load.
peer fabric. The fabric on which an operation is not taking place. The X and Y fabrics are
peers. If an action is being performed on one fabric, the other fabric is the peer fabric.
peer service processors. A pair of service processors (X and Y) in a service processor
(SP) domain. Peer service processors function similarly to a fault-tolerant process pair
in an HP NonStop™ K-series system. See also service processor (SP)
.
pending incident report. An incident report that has never been delivered to your service
provider, either because delivery to both the primary and backup dial-out points was
unsuccessful or because the incident report was generated at an unattended site.
pending signal. A signal that has been generated for a process but has not been delivered.
Pending signals are usually blocked signals.
periodic incident report. A type of incident report that is generated periodically to test the
connection to the service provider and report the current system configuration. The
default frequency is 20 days.
peripheral enclosure. An enclosure that contains components related to one or more
peripherals. The 519x tape subsystem is an example of a peripheral enclosure.
Peripheral enclosures are not part of the set of system enclosures. Contrast with
system enclosure
.
Peripheral Utility Program (PUP). A utility used in D-series and earlier release version
updates (RVUs) to manage disks and other peripheral devices. In G-series RVUs,
similar functions are performed by the Subsystem Control Facility (SCF).
persistence. For the Subsystem Control Facility (SCF), the capability of a generic process
to restart automatically if it was stopped abnormally. You configure this capability by
specifying a nonzero AUTORESTART value in an ADD command.
persistence count. The number of times the $ZPM persistence manager process will
restart a generic process that has been terminated abnormally. A generic process with
an AUTORESTART value of 10 (the maximum) is said to have a persistence count of
10. See also persistence
.