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-21
13. Update SP Firmware in Enclosure If Necessary
13. Update SP Firmware in Enclosure If
Necessary
You might be able to skip this step:
To update the SP firmware on the enclosure to be added, complete the following
procedure for both its CRUs:
Note. For IOAM enclosures, your service provider must verify that the ME firmware and the
ME FPGA is the latest version. Updating the ME firmware and ME FPGA is described in the
Modular I/O Installation and Configuration Guide.
If SP Firmware Versions Are … Then …
Identical on the enclosure to be added and
the target system
Skip this step. Go to Step 14. Configure
Topology of Enclosure If Necessary on
page 6-22.
Different on the enclosure to be added and
the target system
Perform this step.
Step Action Result (page 1 of 2)
1. On the system console attached to this
enclosure, from the OSM or TSM Low-
Level Link, click SP Actions.
If system discovery has occurred, select
Display > SP Actions
The Service Processor Actions dialog
box appears.
2. In the Service Processors (SPs) list, select the service processor in slot 50 for the
enclosure you are adding.
3. In the Actions list, select Firmware Update.
4. Click Browse. The Open dialog box appears.
5. Navigate to and open the spcode9 directory (created in Step 2
on page 6-13).
6. Double-click the spntcde9 SP firmware file.
7. Click Perform Action. A warning appears that the update
might take up to 30 minutes.
8. Click OK. The status line tracks the update.
9. When the status of the update is
Completed, click OK.
The Actions menu of the Service
Processor Actions dialog box
reappears.
10. Select Reset.
11. Click Perform Action.
12. Click OK. Even though the request is labeled
Completed, the action itself takes up to
two minutes to finish.