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

The Resizing Process
HP NonStop S-Series System Expansion and Reduction Guide—522465-009
1-2
Prerequisites
Prerequisites
To resize a NonStop S-series system online:
Also, it is recommended, but not required, that you complete a NonStop S-series
support class before you resize a system.
Expansion With IOAM Enclosures
You can use I/O Adapter Module (IOAM) enclosures installed in 19-inch racks or
modular cabinets to expand your system. An IOAM enclosure connects to the MSEB of
S76000 and later S-series systems.
Each IOAM enclosure can accept up to 10 ServerNet adapters designed specifically
for the IOAM enclosure. These include the Fibre Channel ServerNet adapter (FCSA)
and the Gigabit Ethernet 4-Port ServerNet Adapter (G4SA).
FCSAs provide access to Fibre Channel storage devices, such as an Enterprise
Storage System (ESS). For more information, see the Fibre Channel ServerNet
Adapter Installation and Support Guide.
G4SAs provide increased Ethernet capacity. An IOAM enclosure with 10 G4SAs
provides up to 40 ports of Gigabit Ethernet connections. For more information, see the
Gigabit Ethernet 4-Port ServerNet Adapter Installation and Support Guide.
You must be familiar with:
•
OSM or TSM software package
•
HP NonStop Kernel operating system
•
Subsystem Control Facility (SCF)
•
NonStop S-series system
The system you are planning
to resize must be:
•
Fully functional
•
Currently running the following software and firmware if
you are planning to reduce the system online:
°
G06.04 or later RVU
°
Compatible version of the OSM or TSM package
°
OSM running on G06.08 or later RVU
The system you are planning
to resize must have:
Identical firmware and boot code on all:
•
Processors
•
Service processors (SPs)
•
SCSI controllers
This guide describes how to make firmware and boot code
identical.
Caution. IOAM enclosures and components are FRUs and must be installed by service
providers trained by HP.