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
OSM, TSM, System, and Firmware Information
(circle one)Target System / Donor System Worksheet 1
OSM Product Version
See the OSM User's Guide and the NonStop System Console Installer Guide for instructions on how to
obtain this information.
TSM Client software on (circle one) target system console / donor system console
TSM Product Version on the System Consoles
For expansion: If the SP firmware of the block does not match the SP firmware of the target
system, you must upgrade the block before continuing.
Group Numbers This system contains these group numbers before resizing (circle all that apply):
01 11 12 13 14 15 02 21 22 23 24 25 03 31 32 33 34 35 04 41 42 43 44 45
05 51 52 53 54 06 61 62 63 64 07 71 72 73 74 08 81 82 83 84
55 56 57 58 59 65 66 67 68 69 75 76 77 78 79 85 86 87 88 89
Current SYSnn
Saved Configuration
Saved Configuration
after Reduction (if applicable)
System Information
System Name
System Serial Number
System Type
Topology
Initial Version:
Needs to Be Upgraded to:
TSM Client software: block system console
Initial Version:
Needs to Be Upgraded to:
Upgraded
Upgraded
VST201.vsd
Tetra 8 Tetra 16
If your system consoles are not running the correct TSM client software for your RVU, upgrade the consoles
with the appropriate NonStop System Console Installer CD-ROM.
SP Firmware Version
ME Firmware Version (IOAM only)
ME FPGA Version (IOAM only)