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

Expanding a System Online
HP NonStop S-Series System Expansion and Reduction Guide—522465-009
6-3
Preparation for Online Expansion
Cautions.
•
You can expand your system only if it already contains an adequate number of MSEBs
and MSEB PICs to support the increased number of processors after expansion.
•
You can expand your system online only if it is running G06.00 or later with a compatible
TSM package or G06.08 or later with a compatible OSM or TSM package.
For information about the OSM package and other requirements for migrating to OSM, see
the OSM Migration Guide.
For information about the TSM package, see the TSM Read Me file at Start > Programs
>Compaq TSM > TSM Documentation > TSM Read Me > TSM Product Version
Information > TSM Software Product Versions. If you are running an RVU earlier than
G06.00, you must expand the system offline, as described in the NonStop S-Series
Planning and Configuration Guide.
•
If you are expanding your system to include IOAM enclosures, you need the G06.24 RVU
or later and the OSM software components that are included with it. The IOAM enclosure
and its components must be installed by a service provider trained by HP.
•
If you are expanding your system, you might need a different topology. Topologies
cannot be changed online. After you configure your system for a particular topology,
changing the topology requires stopping your system. For more information, see the
NonStop S-Series Planning and Configuration Guide.
•
It is critical to set the topology value (Tetra 8 or Tetra 16) correctly on each enclosure you
add. These values must match the value on the target system.
•
Ensure you have KMSF swap files of the proper size and location available on both
systems. Otherwise, applications and processes on the newly resized systems might
terminate. For information about KMSF swap files and their recommended sizes, see the
Kernel-Managed Swap Facility (KMSF) Manual.
•
When you attach ServerNet cables between the block and the target system, you must
attach all cables correctly the first time. If you attach the cables to the wrong ports, perform
the recovery described in ServerNet Fabrics Are Cross-Cabled
on page 7-10.
•
The SP firmware on all blocks to be added must be identical to the SP firmware on your
target system.
•
Do not unplug and replug any AC power cords. If you do, see AC Power Cord Was
Unplugged or Replugged on page 7-2. After any enclosure has been plugged into an AC
power source once, unplugging and then replugging its AC power cord powers on the
enclosure prematurely.
•
If you are expanding your system with enclosures taken from another system, plug in their
AC power cords last, after you have completed all other steps.