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-14
6. Finish Gathering Information
6. Finish Gathering Information
At this stage, you treat and configure each enclosure separately. Before you configure
an enclosure into a block, you must supply its IP information. IP information for an
enclosure is recorded on different worksheets, depending on whether the enclosure
came directly from the factory or from a donor system.
Make a copy of Worksheet 7 and keep it accessible. You will use it later when you
configure the enclosures into a block.
If Enclosure Comes From the Factory
If the enclosure was shipped directly from the factory, it contains default IP addresses.
These addresses are listed in Table 6-3 and preprinted on Worksheet 7.
If Enclosure Comes From a Donor System
If the enclosure is coming from a donor system, you already recorded the slot 50 and
slot 55 IP addresses on Worksheet 2.n of the donor system packet during Step
2.1 Record Basic Information on page 4-4.
Contact your network administrator to identify the subnet mask and gateway route
IP addresses for the donor system.
On Worksheet 7 of the donor system packet, record these values and the information
from Worksheet 1.
Note. IP addresses for the ServerNet switch boards of the IOAM enclosures are dynamically
assigned by a DHCP server or software that performs the same function.
Table 6-3. Default MSP IP Addresses
Item Value
Slot 50 192.231.36.2
Slot 55 192.231.36.3
Subnet Mask 255.255.255.0
Gateway Route 192.231.36.9