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
Reducing a System Online
HP NonStop S-Series System Expansion and Reduction Guide—522465-009
4-19
9. Finish the Reduction
9. Finish the Reduction
9.1 Save New Donor System Configuration
Now that you have altered the donor system’s configuration, save its current
configuration.
1. At a TACL prompt, start SCF and enter the SAVE CONFIGURATION command:
>SCF
-> SAVE CONFIGURATION xx.yy
where xx.yy is a configuration number in the range 00.00 through 99.99 that is
both:
•
Not already in use
•
Not the configuration number you used in Step 1.3 Save the Current Donor
System Configuration on page 4-3
If you specify a number that is already in use, you receive this message:
Configuration file $SYSTEM.ZSYSCONF.CONFxx.yy already exists.
Replace it (Y/[N])
2. Enter N and retry the SAVE CONFIGURATION xx.yy command using another
number.
3. Record the number of your saved configuration (xx.yy)on Worksheet 1.
9.2 Maintain System Console Connections
If your donor system will remain in use, it is recommended that you maintain the
following sessions on a system console so that you can monitor events on this donor
system:
•
CLCI (Startup TACL) connection
•
CNSL (EMS Event Stream) connection
•
OSM or TSM Low-Level Link
•
OSM Service Connection or TSM Service Application