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-78
power shelf
of the batteries, fans, and power supplies; to regulate the voltage supplied to the fans;
and to provide the interface to the group ID switches and service light-emitting diodes
(LEDs). A group contains two PMCUs, one for each of the two DC power distribution
buses.
power shelf. In HP NonStop™ S7400, S7600, and Sxx000 processor enclosures and I/O
enclosures containing I/O multifunction (IOMF) 2 customer-replaceable units (CRUs),
an assembly residing below the chassis consisting of power supplies and supporting
circuitry that provides DC power to the enclosure.
power supply. (1) In system enclosures without power shelves, the component on the
processor multifunction (PMF) customer-replaceable unit (CRU) or the I/O
multifunction (IOMF) CRU that converts standard AC line voltage into the DC voltages
needed by the group components in the enclosure. (2) In system enclosures with
power shelves, the component located in the power shelf that converts standard AC
line voltage into DC voltage and delivers it to the PMF CRUs or IOMF CRUs in that
enclosure, which in turn supply the DC voltages needed by the group components in
the enclosure.
PPL. See process-pair list (PPL).
PPP. See Point-to-Point Protocol (PPP).
preemption. A form of late binding in which a symbolic reference to a symbol defined in the
same dynamic-link library is instead bound to a definition in another loadfile.
preferences file. A file that contains configuration information for the graphical user
interface (GUI) portion of the OSM and TSM client software. The preferences file is
used by the OSM and TSM client software at system startup.
preferred path. See primary path.
preprocessing commands. Commands specifying unique run-time parameters that can
override your default system parameters. These commands can assign process file
names, select backup media formats, and define utility options during system
configuration.
preset. A linker operation that sets the correct values (addresses) of imported symbols
according to the environment seen by the linker. If the loader encounters the same
environment at load time, it avoids adjusting these values, which reduces loading
overhead. (See
fastLoad.) If not, the loader resets these values to match the load-time
environment.
primary path. A path enabled as the preferred path. When a primary path is disabled, an
alternate path
becomes the primary path.
primary processor. The processor that is designated as owning the ServerNet addressable
controller (SAC) connected to separate processors running the HP NonStop™ Kernel