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
 

Expanding a System Online
HP NonStop S-Series System Expansion and Reduction Guide—522465-009
6-26
17.2  Verify ServerNet Cabling
4. Connect the system console to the block. You performed these procedures for 
each of the enclosures you have prepared. Now you perform these procedures for 
the entire block. 
17.2  Verify ServerNet Cabling
To be sure that enclosures within the block are cabled correctly, verify the ServerNet 
cabling by performing this step for each PMF CRU and IOMF CRU in the block: 
17.3 Power Off Block
Power off the block, as described in 15. Power Off Enclosure on page 6-23.
Step Page
7. Connect a System Console to the Enclosure
6-15
9. Power On Enclosure 6-17
Start the OSM or TSM Low-Level Link A-9
10. Verify Connection Between System Console and Enclosure 6-18
Step Action Result
1. From the OSM or TSM 
Low-Level Link, select the 
Display menu and click SP 
Actions.
The Service Processor Actions dialog box 
appears.
2. From the Service Processor (SPs) list, select an SP for an enclosure in the block 
you are adding.
3. From the Actions list, select SP Responsive Test.
4. Click Perform action. When the action is completed, the status is 
listed as Completed in the Action Status box.
5. Repeat this procedure from Step 2 for the other PMF CRU or IOMF CRU in the 
enclosure.
6. Repeat this procedure from Step 2 for every other enclosure in the block you are 
adding.
Note. For IOAM enclosures, your service provider must verify the ServerNet cabling by using 
the ME Responsive Test of the OSM Low-Level Link Application.










