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-35
23b. Update Firmware and Code in Block (Using
OSM)
23b. Update Firmware and Code in Block
(Using OSM)
Do this step even if you performed 13. Update SP Firmware in Enclosure If Necessary.
For each PMF CRU or IOMF CRU in each enclosure you added, check (and update if
necessary) the SP firmware, processor boot code, and SCSI boot code:
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.
Step Action Result
1. In the OSM Service Connection, from the
Display menu, select Multi-Resource Actions.
The Multi-Resource Actions
dialog box appears.
2. From the Resource Type drop-down list, select
SP.
3. Select Processor Boot Millicode Firmware
Update from the Action drop-down list.
4. In the list of SPs, scroll to find the Processor Boot Millicode Firmware attributes 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 4a through 4e.
•
If the Version is the same as or newer than the Default File Version, skip to
Step 5.
a. Select the SP you need to update and click Add. 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.
e.
Perform a hard reset of the processor (do not
close the OSM Service Connection session or the
Multi-Resource Actions dialog box; you will use it
again in Step 5):