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

Troubleshooting
HP NonStop S-Series System Expansion and Reduction Guide—522465-009
7-6
CRU Does Not Start
CRU Does Not Start
In Step 9. Power On Enclosure on page 6-17, when you press the power-on button on
one PMF CRU or IOMF CRU, the other PMF CRU or IOMF CRU in the same
enclosure does not power on.
Cause
The PMF CRUs or IOMF CRUs in a single enclosure might not be seated correctly.
Recovery
1. Unseat the affected CRU and wait one minute.
2. Reseat the CRU and reattach the AC power cord within 25 seconds.
The CRU performs a POST. If an amber LED stays on for longer than five minutes,
see POST Fails on page 7-9.
If the problem persists, contact your service provider.
IP Address Already Exists
During Step 11. Configure System Console and Enclosure on page 6-19, when you
attempt to add the IP addresses of the enclosures in the block in the OSM or TSM
Low-Level Link, you get this message:
You have entered IP addresses that already appear in the current
system list. Do you want to continue?
This is a normal message.
Cause
The enclosures in the block to be added have the same low-level link IP address (as
with new enclosures, for example).
Recovery
1. In answer to the question, click Yes.
2. The Edit Systems List dialog box then displays the added enclosure with the name
“New System.” Click OK.
3. In the OSM or TSM Low-Level Link, log on to New System. The new system entry
is no longer listed in the Edit Systems List dialog box.
If the system console you are using is the system console and you are moving it
from the target system, the donor system, or the enclosure, you might have to re-
add the IP address later when you reattach the system console to the target
system.