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-18
10. Verify Connection Between System Console and
Enclosure
10. Verify Connection Between System
Console and Enclosure
In this step, you check whether the system console and enclosure you have connected
are communicating.
10.1 Verify Connection to ServerNet X Fabric
Open a Command Prompt window on the system console and enter the following
command using the low-level link IP address of group 01, slot 50, from Worksheet 2.1:
C:\>ping IP-address-of-the-SP-in-slot-50
The following example is the display you see if the system console is connected to the
ServerNet X fabric:
If you receive any other messages, see Ping Command Does Not Work on page 7-7.
10.2 Verify Connection to ServerNet Y Fabric
Enter the following command with the low-level link IP address of group 01, slot 55,
from Worksheet 2.1:
C:\>ping IP-address-of-the-SP-in-slot-55
The following example is the display you see if the system console is connected to the
ServerNet Y fabric:
If you receive any other messages, see Ping Command Does Not Work on page 7-7.
C:\>ping 192.231.36.2
Pinging 192.231.36.2 with 32 bytes of data:
Reply from 192.231.36.2: bytes = 32 time = 10ms TTL = 60
Reply from 192.231.36.2: bytes = 32 time = 30ms TTL = 60
Reply from 192.231.36.2: bytes = 32 time = <10ms TTL = 60
Reply from 192.231.36.2: bytes = 32 time = 30ms TTL = 60
C:\>ping 192.231.36.3
Pinging 192.231.36.3 with 32 bytes of data:
Reply from 192.231.36.3: bytes = 32 time = 60ms TTL = 60
Reply from 192.231.36.3: bytes = 32 time = 11ms TTL = 60
Reply from 192.231.36.3: bytes = 32 time = 40ms TTL = 60
Reply from 192.231.36.3: bytes = 32 time = <10ms TTL = 60