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

Planning System Reduction
HP NonStop S-Series System Expansion and Reduction Guide—522465-009
3-6
Determining Communication Paths
Determining Communication Paths
You must determine the direct and indirect communication paths within your donor
system so that you know which enclosures to prepare for online reduction. To trace the
ServerNet connections among enclosures, see Worksheets 9, 10, and 11 in
Appendix C.
When you see from these worksheets which enclosures might be affected by system
reduction, determine with your system analyst or service provider what processes and
other devices might also be affected.
Because the adapters and communications devices in each system are configured
uniquely to that system, these worksheets cannot show every possible direct or indirect
connection. For example, SWAN concentrators might be connected to your system in
several places.
Example Using the ServerNet Worksheets
This subsection illustrates the following steps in completing a ServerNet worksheet:
These worksheets illustrate the maximum configuration of each topology. Your system
might contain fewer enclosures. You must note what your system currently contains to
trace the pathways of ServerNet communication accurately.
For Information About See
The definition of an indirect
communication path
Indirect Communication Paths
on page 3-4
ServerNet connection paths in detail NonStop S-Series Planning and Configuration Guide
Note. The cabling diagrams in this guide identify all ServerNet expansion boards as SEBs.
Your system might have or require modular ServerNet expansion boards (MSEBs) in the slots
designated for SEBs. SEBs and MSEBs are functionally equivalent.
Step Page
1. Choose and Copy the Appropriate Worksheets
3-7
2. Highlight Your Present System Configuration 3-8
3. Black Out the Enclosures to Be Removed 3-10
4. Trace Communication Paths to Each Enclosure 3-11
5. Circle the Affected Enclosures 3-13
6. List Affected Enclosures in Reverse Numerical Order 3-15