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

Glossary
G-Series Common Glossary
Glossary-9
branch circuit
branch circuit. The circuit conductors located between the equipment receptacles and the
final overcurrent device in a power distribution panel (PDP) that protect the circuits.
branded product. A software product that is licensed by X/Open to carry the X/Open or
UNIX trademark.
branding process. The activities that lead to the acceptance of a product by X/Open in
accordance with its Trade Mark Licence Agreement.
break condition. An event indicator or sequence of data from a terminal or terminal
emulator that requests interruption of an application program.
bridge rectifier. A full-wave rectifier with four elements, as in a bridge circuit. Alternating
voltage is applied to one pair of opposite junctions, and direct voltage is obtained from
the other pair of junctions.
BSD. Berkeley Software Distribution.
built configuration. A configuration revision for which a system image and activation
package have been created.
built-in command. In the Open System Services (OSS) environment, a command that is
implemented within the
/bin/sh file. Some built-in commands are also available as
separately executable files.
bypass mechanism. Equipment that permits switching from one power source to another.
For example, a bypass mechanism on an uninterruptible power supply (UPS)
would
switch to an alternative power source (such as a standby power generator or
commercial utility source) when maintenance must be performed on the UPS.
byte-synchronous. A type of Open Systems Interconnection (OSI) Layer-2 protocol that
uses synchronous transmission techniques and requires a character code to define
terminal and line control sequences. Data is always transmitted in a block.
cabinet. One or more modules of a system, housed together.
cable channel. A cable management conduit that protects the cables that run between two
system enclosures in a double-high stack. Each system enclosure has two cable
channels running vertically on its service side: one on the left-hand side of the
enclosure, and one on the right-hand side of the enclosure.
cable guidepost. A cable management rod that routes cables exiting the upper enclosure
in a double-high stack to prevent the cables from hanging down in front of the
customer-replaceable units (CRUs) in the base enclosure. A cable guidepost extends
from the base of each cable channel.
cable support. A piece of cable management hardware that secures system cables. The
cable support attaches to the service side of a system enclosure near the bottom of the
enclosure. Cable ties for securing system cables are threaded through the cable