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-5
Top ol ogy
Topology
The topology of your system is the basic structure of your system.
Your system can be configured for either of two topologies: Tetra 8 or Tetra 16. Each
topology has advantages, depending on how you use your system and how you plan to
resize it in the future.
If you are expanding your system, you might need a different topology. For example, if
your system is a Tetra 8 topology with the maximum number of I/O and processor
enclosures attached, you cannot expand it online. You must reconfigure it offline as a
Tetra 16 before it can support more enclosures.
Choosing a Topology
NonStop S-series servers are shipped with Tetra 8 topology unless the system ordered
specifically requires more than eight processors or needs to be able to grow online to
more than eight processors.
When planning to resize your system, consider which of the following cases your
system fits:
Case 1 is clear. In Case 2, you must make decisions:
1. Estimate your rate of future system growth.
2. Decide whether your system growth will ever require a change in topology.
3. Decide whether the present cost of buying additional hardware in a new Tetra 16
system is less than the future cost of a system outage.
Note. It is important to decide ahead of time which system topology you want in your
resized system because topologies cannot be changed online. After you configure your
system for a particular topology, changing the topology requires stopping your system.
For Information About See
Topologies NonStop S-Series Planning and Configuration Guide
Case Description Examples
1 The system’s topology does not
need to change.
•
The system starts as a Tetra 8 topology
and will never get too large to be a Tetra
16 topology.
•
The system starts and stays as a Tetra 16
topology.
There is no advantage to changing to a
Tetra 8 even if the system is reduced.
2 The system’s topology must
change between a Tetra 8 and a
Tetra 16.