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-11
ServerNet Fabrics Are Down
Recovery
1. Disconnect ServerNet cables between the target system and the affected block.
2. Unplug the AC power cords of the affected block.
3. Unplug the battery packs in the affected block.
4. Replug battery packs in the affected block.
5. Begin the resizing process again at 20. Power On Added Block on page 6-28.
ServerNet Fabrics Are Down
One or more ServerNet fabrics might be down.
Cause
This can happen either:
•
On a system running a RVU earlier than G06.04
•
If a fabric was brought down manually
Recovery
1. Enter the following command and check for any status other than UP.
> SCF STATUS SERVERNET $ZSNET
2. Start any down fabrics:
> SCF START SERVERNET $ZSNET.X.*
> SCF START SERVERNET $ZSNET.Y.*
3. Return to Step 3.2 Eliminate Problems in the ServerNet Fabrics on page 4-6.
If the problem persists, contact your service provider.
Slots 50 and 55 Remain Unlisted for an Enclosure
After you connect the block to the target system, an SCF STATUS ADAPTER
command does not list slots 50 and 55 for one or more enclosures in the block.
Cause and Recovery
See Added Enclosure Is Not Recognized by the Target System on page 7-4.