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
Reducing a System Online
HP NonStop S-Series System Expansion and Reduction Guide—522465-009
4-2
1. Prepare the Donor System for Reduction
1. Prepare the Donor System for Reduction
1.1 Prepare Worksheets
1. From Appendix C, make copies of Worksheet 1 and Worksheets 2.1 through 2.8
(referred to hereafter as Worksheets 2.n).
If the system contains any IOAM enclosures, also make copies of Worksheet 2.1a.
2. Circle the words Donor System at the top of each worksheet.
3. Make one copy of Worksheet 8 in Appendix C for each enclosure you will remove.
If any of the enclosures is an IOAM enclosure, make a copy of Worksheet 8a.
4. Staple these worksheets together into a donor system packet.
If you will be adding these enclosures to another (target) system, be sure to keep this
donor packet separate from worksheets for the target system. It is important not to mix
information from your target system with information from your donor system.
1.2 Upgrade OSM or TSM Software If Necessary
OSM Client Software
To determine whether the OSM Client Software components need to be upgraded:
OSM Console Tools
HP recommends that you install the OSM Console Tools to get the most recent versions of the
OSM Service Connection and the OSM Event Viewer. See the NonStop System Console
Installer Guide.
Step Action Use This Procedure
1. Determine the current version of
the OSM Client software
components.
Determine the Product Versions of the OSM
Client Software on page A-7.
2. Determine whether you are running
the latest versions of the client
software.
See
the OSM Migration Guide
3. Upgrade the client software, if
necessary
See the NonStop System Console Installer
Guide.