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-4
Added Enclosure Is Not Recognized by the Target
System
Added Enclosure Is Not Recognized by the Target System
The OSM or TSM applications on the target system do not show the enclosure you just
added. This problem might occur during Step 22.1 Verify That Added Enclosures
Appear in System Configuration on page 6-31.
Cause and Recovery
If the preceding recovery procedures do not work, contact your service provider.
Cause Recovery
Topology problem.
The topology value for the
added block, as specified
in the OSM or TSM
Low-Level Link, does not
agree with your target
system’s value.
1. Unplug the AC power cords of the affected block or
enclosure.
2. Unplug the battery packs from the power monitor and
control unit (PMCU) in the affected block or enclosure.
3. Replug the battery packs into the PMCU in the affected
block or enclosure, but do not plug in the AC power cords
yet.
4. Attach a system console. See Step 7 on page 6-15
.
5. Change the group ID to 01. See Step 8 on page 6-16
.
6. Power on the enclosure. See Step 9 on page 6-17
.
7. Correct the topology value of the enclosure. See Step 14
on page 6-22
.
8. Resume the expansion procedure at Step 15. Power Off
Enclosure on page 6-23.
ServerNet fabrics are
cross-cabled.
See ServerNet Fabrics Are Cross-Cabled
on page 7-10.
Resume the expansion procedure at Step 20. Power On Added
Block on page 6-28.
AC power cords are
unplugged.
See AC Power Cord Was Unplugged or Replugged
on
page 7-2.
Power-on cables are
disconnected.
See Added Enclosure Does Not Power On
on page 7-3.
The enclosure has an
incorrect group ID switch.
1. Unplug the AC power cords of the affected block or
enclosure.
2. Unplug the battery packs from the power monitor and
control unit (PMCU) in the affected block or enclosure.
3. Replug battery packs into the PMCU in the affected block
or enclosure, but do not plug in the AC power cords yet.
4. Resume the expansion procedure at Step 18. Change
Group Numbers of Block to Fit Target System on
page 6-27.
Malfunctioning hardware. Contact your service provider.