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-5
1. Prepare Target System for Expansion
Table 6-2. Preparatory Steps
Step Action Reason
1. If necessary, upgrade the OSM or
TSM client software to a compatible
version on all system consoles used
in the resizing process.
For online resizing to succeed, every
system console involved must run identical
versions of the OSM or TSM package.
To determine which product versions of the
OSM package are compatible with your
system, see the OSM Migration Guide.
To determine which product versions of the
TSM package are compatible with your
system, see the TSM Read Me file at Start
> Programs > Compaq TSM > TSM
Documentation.
For instructions about upgrading the OSM
or TSM client software, see the NonStop
System Console Installer Guide.
2. If you are expanding your system with
enclosures from another system,
have handy the donor system packet,
as described in Step 1.1 Prepare
Worksheets on page 4-2.
You need a record of configuration
information about the enclosures from the
donor system.
3. If you are planning a block that
contains more than three enclosures,
make an extra copy of Worksheet 7
for every two additional enclosures.
Worksheet 7 records information for a
maximum of one processor enclosure and
two I/O enclosures. Larger blocks require
more copies of this worksheet.
4. Place the enclosures to be added
near the target system in the same
physical arrangement they will have
after resizing is complete.
This practice minimizes recabling and
troubleshooting.
5. Label all ServerNet cables. Do not cross-cable the ServerNet X and Y
fabrics. Figure 6-1
shows an example of a
simple label: a piece of tape with X or Y
written on it, attached to the cable.
Figure 6-1. Examples of Labeled ServerNet Cables
Y
X
VST107.vsd