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
HP NonStop S-Series System Expansion and Reduction Guide—522465-009
B-1
B ServerNet Cabling
This appendix shows diagrams of all ServerNet cable connections. It also includes
examples of how you can map these diagrams to actual NonStop S-series enclosures.
Example Includes …
Correlation Between Cabling
Diagram and One Enclosure with
SEBS
•
A sample ServerNet cabling diagram of one
enclosure with connections shown to a SEB
•
The service side of a processor enclosure
•
How the diagram relates to the components in the
enclosure
•
Table B-1, Router Port Connections to SEBs
Correlation Between Cabling
Diagram and One Enclosure with
MSEBS
•
A sample ServerNet cabling diagram of one
enclosure with connections shown to an MSEB
•
The service side of a processor enclosure
•
How the diagram relates to the components in the
enclosure
•
Table B-2, Router Port Connections to MSEBs
Correlation Between Cabling
Diagram and Two Enclosures
•
A sample ServerNet cabling diagram of two
connected enclosures
•
A processor enclosure connected to a NonStop
S-series I/O enclosure
•
How the diagram relates to the components in each
enclosure and the connections between them
Cabling Diagram
NonStop S-Series System — Tetra 8 Topology, X Fabric
NonStop S-Series System — Tetra 8 Topology, Y Fabric
NonStop S-Series System — Tetra 16 Topology, X Fabric
NonStop S-Series System — Tetra 16 Topology, Y Fabric
Note. The Tetra 16 cabling diagrams show the maximum possible number of I/O enclosures.
Your service provider can tell you the number of I/O enclosures supported by the RVU running
on your system.
Note. The diagrams in this guide identify all ServerNet expansion boards as SEBs. Your
system might instead have or require modular ServerNet expansion boards (MSEBs) in the
slots designated for SEBs. SEBs and MSEBs are functionally equivalent.
Caution. ServerNet cabling for IOAM enclosures is different from the cabling shown in this
Appendix. Only service providers trained by HP should perform cabling of IOAM enclosures.