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-36
23b. Update Firmware and Code in Block (Using
OSM)
1. Launch and log on to the OSM Low-Level
Link.
2. Click Processor Status. The Processor Status dialog
box appears.
3. Click to select the processor you want to
update.
4. From the Processor Actions list, select Hard
Reset and then click Perform action.
After one to three minutes, the
Action Status box indicates a
successful Hard Reset.
5. When the status line lists the action as Completed, click Close.
If the action does not complete successfully, see Action Detail for more
information.
5. Return to the Multi-Resource Actions dialog box. Select SCSI Boot Code Firmware
Update from the Action drop-down list.
6. Check the SCSI Boot Code Firmware attributes for the same SP and compare the
Version attribute to the Default File Version.
•
If the Version is older than the Default File Version, the Version is down-rev
and should be updated. Perform Steps 6a through 6e.
•
If the Version is the same as or newer than the Default File Version, skip to
Step 7.
a. If the SP you want to update is not already in the
lower list, select the SP and click Add to move it
to the lower list.
The SP moves to the lower list.
b. Click Perform Action. After a confirmation dialog, a
Parameter Input dialog box
allows you to specify an
alternate file location for the
version to use for the update.
c. Enter a location or leave it blank if you are using
the default location, and click OK to perform the
update.
The Progress bar at the bottom
of the Multi-Resource Actions
dialog box indicates the pass or
fail status of the action.
d. When the action completes, check the Processor
Boot Millicode Firmware attributes again to
confirm that the Version now matches the
Default File Version.
If the action fails, click Action Summary and
then Details to get more information about why
the action failed.
7. For the PMF CRU in slot 55 of the enclosure you
added, repeat this procedure from Step 3.
8. If you added any other enclosures, repeat this
procedure for each enclosure from Step 1.
Step Action Result