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-12
5.2 Identify IP Address for FTP Session
A display such as the following can take a few moments to appear:
3. Note the adapters named \system-name.LANX or \system-name.LANY. Do not
use either of these adapters to copy SP firmware.
4. Ask your network administrator which one of the other adapters should be used to
create a file transfer protocol (FTP) session between the system console and the
target system. In this example, the E4SA device is \TROLL.LAN670A, shown in
boldface. Its IP address of 172.17.116.175 is used in the next step.
->INFO SUBNET $*.*
TCPIP Info SUBNET \TROLL.$ZTC00.*
Name Devicename *IPADDRESS TYPE *SUBNETMASK SuName QIO *R
#LOOP0 \NOSYS.$NOIOP 127.0.0.1 LOOP-BACK %HFF000000 OFF N
#SN1 \TROLL.LAN670A 172.17.116.175 ETHERNET %HFFFFFF00 ON N
TCPIP Info SUBNET \TROLL.$ZTC20.*
Name Devicename *IPADDRESS TYPE *SUBNETMASK SuName QIO *R
#LOOP0 \NOSYS.$NOIOP 127.0.0.1 LOOP-BACK %HFF000000 OFF N
#SN1 \TROLL.LAN020A 172.17.116.190 ETHERNET %HFFFFFF00 ON N
TCPIP Info SUBNET \TROLL.$ZTCP0.*
Name Devicename *IPADDRESS TYPE *SUBNETMASK SuName QIO *R
#LOOP0 \NOSYS.$NOIOP 127.0.0.1 LOOP-BACK %HFF000000 OFF N
#SN1 \TROLL.LANX 172.17.116.173 ETHERNET %HFFFFFF00 ON N
TCPIP Info SUBNET \TROLL.$ZTCP1.*
Name Devicename *IPADDRESS TYPE *SUBNETMASK SuName QIO *R
#LOOP0 \NOSYS.$NOIOP 127.0.0.1 LOOP-BACK %HFF000000 OFF N
#SN1 \TROLL.LANY 172.17.116.174 ETHERNET %HFFFFFF00 ON N