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-12
Code 316 Returned During Logon
Code 316 Returned During Logon
While trying to log on to the OSM or TSM Low-Level Link during Step 12.1 Determine
SP Firmware Version for Enclosure on page 6-20, you get a code 316 error message
on the status bar at the bottom of the OSM or TSM window.
Cause
You are trying to configure an enclosure or block before adding it to a target system,
but the system console does not recognize the enclosure you are trying to configure
because you are connected to a group other than group 01.
Recovery
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. Return to Step 8. Change Group Number of Enclosure to 01 on page 6-16.
Perform this step and all subsequent steps again.
Startup TACL Window Does Not Open
You cannot open a startup TACL window using the procedure Start a Startup TACL
Session on page A-9.
Cause and Recovery
If the preceding recovery procedures do not work, contact your service provider.
Cause Recovery
1. You get a “duplicate CLCI request”
message, indicating that a startup TACL
window is already open.
This message also gives you the IP
address of the workstation that currently
owns the startup TACL, from which you
can find the workstation.
2. The startup TACL window has no TACL
prompt because you attempted to open
a startup TACL window on the wrong
ServerNet fabric.
This is the backup fabric window.
Minimize it to see the primary fabric
window.