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-6
Impact on Users
Benefits of Different Topologies
The benefits of Tetra 8 topology are:
•
ServerNet adapters can be put in slots that in Tetra 16 topology are reserved for
SEBs and MSEBs.
•
If your current needs are satisfied by a Tetra 8 topology, you do not have to
purchase the extra hardware that a Tetra 16 topology requires.
The benefits of Tetra 16 topology are:
•
You are not limited to the Tetra 8 maximums of eight processors and two I/O
enclosures per processor enclosure.
The number of I/O enclosures that a processor enclosure can support varies
depending on the RVU of your system. Your service provider can tell you the
number of I/O enclosures supported by the RVU that is running on your system.
•
The system can be expanded without a system outage.
Impact on Users
For system resizing to have minimal impact on users and processes, perform online
reduction and expansion tasks during periods of low use (that is, during nonpeak
hours).
System Availability
The availability of your system is determined by the communication among its:
•
Enclosures
•
Disks
•
Processor multifunction (PMF) CRUs
•
I/O multifunction (IOMF) CRUs
•
IOAM enclosures (if used)
•
Peripheral devices
•
Subsystems
For Information About See
Online reduction tasks Section 4, Reducing a System Online
Online expansion tasks Section 6, Expanding a System Online
Caution. When you resize your system, you alter some or all of these paths of
communication. Unless you plan your resizing carefully, you might disrupt
communications in your system and reduce your system’s availability.