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

Reducing a System Online
HP NonStop S-Series System Expansion and Reduction Guide—522465-009
4-8
5. Prepare and Stop Devices and Processes
5. Prepare and Stop Devices and Processes
Because you must maintain access to the system after you have stopped or moved all
devices, processes, and their communication paths, the TACL process you use for the
following steps should run in group 01. For this reason, use the startup TACL process
for system reduction.
Step Action
1. Using OSM or TSM and Worksheet 8, collect information about the following
devices in the enclosure to be removed:
•
Internal disk drives
•
Adapters (in direct or indirect communication with devices):
°
ServerNet adapters
°
SEBs or MSEBs (This information is used only for determining
communication paths. SEBs and MSEBs are not moved or terminated.)
•
SWAN concentrators
•
External tape drives
•
Open SCSI devices
For IOAM enclosures, collect information about ServerNet Switch Boards, FCSAs,
and G4SAs on Worksheet 8a.
2. Identify any dependent processes and indirect communication paths before
removing an enclosure:
a. To identify currently running processes in a processor enclosure, use the
TACL STATUS command on that enclosure. For example:
> STATUS 8
b. Correlate the list of processes returned with the results of Step 4. Inventory
Enclosures to Be Removed on page 4-7.
c. Identify processes and paths that might be affected.
3. Terminate or move processes as necessary.
For Information About See
Establishing a startup TACL
connection
Start a Startup TACL Session
on page A-9
Examples of preparing and
stopping devices and their
associated processes
Appendix D, Stopping Devices and Processes
Documentation you might
need for your subsystems
Table D-1, References and Examples, on page D-1
Indirect communication paths Is the Enclosure Providing Critical Resources?
on page 3-4
Determining Communication Paths
on page 3-6