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-11
5. Copy SP Firmware File From the Target System to
the System Console
5. Copy SP Firmware File From the Target
System to the System Console
In this step, you shift your activities from the target system to the block you will add. If
you have a system console to move from the target system to that block, this step
indicates when to move the system console.
The block you add to your target system must have SP firmware running on the
dedicated LAN that is identical to the SP firmware on the target system. This step
copies the target system’s SP firmware file onto a system console. This file, in turn, is
copied to all enclosures in the block.
5.1 Choose System Console to Use
You can use one of the following system consoles:
•
One of the two system consoles attached to your donor or target system.
•
The one system console that is attached to your target or donor system. However,
if you use the only system console from either system for this operation, you leave
that system without dial-in/dial-out capability until you reconnect the system
console.
When you have chosen the system console you will use, attach it to the target system
if necessary, using the procedure Move the System Console on page A-8.
5.2 Identify IP Address for FTP Session
You will copy the SP firmware file from the target system to the system console through
a dedicated communications adapter such as an E4SA. On the system console on the
target system, determine the IP address of the adapter you will use:
1. Log on to TACL and start SCF.
2. Enter the following SCF command to display IP addresses for the dedicated
communications adapters on the target system:
-> INFO SUBNET $*.*