NonStop S-Series System Expansion and Reduction Guide

Table Of Contents
Expanding a System Online
HP NonStop S-Series System Expansion and Reduction Guide522465-009
6-6
2. Record Information About Target System
2. Record Information About Target System
Before you physically add enclosures to your target system, you must record
information about the target system on worksheets in Appendix C. You determine this
information with a system console.
While you are recording information for the target system, someone else can be
recording the same information for the enclosures to be added to the target system.
This process is described in Step 6. Finish Gathering Information on page 6-14.
2.1 Prepare Worksheets
1. From Appendix C, make copies of Worksheet 1, Worksheets 2.1 through 2.8, and
Worksheet 7. If the target system contains any IOAM enclosures, also copy
Worksheet 2.1a.
2. Circle the words Target System at the top of each worksheet.
3. Staple these worksheets together into a target system packet.
Keep this packet separate from the worksheets for the donor system, if any. Do not mix
information from your target system with information from your donor system.
2.2 Record Information About the Master Service Processor
Record the following information for the master service processor in group 01:
For information about … See …
Starting the OSM or TSM
Low-Level Link
Start the OSM or TSM Low-Level Link
on page A-9
Locating OSM or TSM views OSM or TSM online help
Step Action Result
1. In the OSM or TSM Low-Level
Link window, click System
Discovery.
After several minutes, the Management window
appears. The Attributes tab displays the following:
System Name
System Serial Number
System Type
Topology
SP Firmware Version (on the status bar at the
bottom of the main window)
2. Record this information on Worksheets 1 and 7 of the target system packet.
Caution. If an enclosure in the target system has a different topology from that of group 01,
this information-gathering procedure will not find the incompatibility. However, this
incompatibility can prevent successful expansion. Recovery requires a system outage and
resynchronizing the topology of all enclosures in the target system.