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-2
absolute pathname
absolute pathname. An Open System Services (OSS) pathname that begins with a
slash (/) character and is resolved beginning with the root directory. Contrast with
relative pathname
.
AC. See alternating current (AC).
accelerated mode. The operational environment in which Accelerator-generated RISC
instructions execute. See also TNS mode
and TNS/R native mode.
accelerated object code. The RISC instructions that result from processing a TNS object
file with the Accelerator program.
accelerated object file. The object file that results from processing a TNS object file with
the Accelerator program. An accelerated object file contains the original TNS object
code, the accelerated object code and related address map tables, and any binder and
symbol information from the original TNS object file.
Accelerator program. A program that processes a TNS object file and produces an
accelerated object file. Most TNS object code that has been accelerated runs faster on
TNS/R processors than TNS object code that has not been accelerated. The
Accelerator program (AXCEL) is run prior to running the accelerated linker, XLLINK.
access mode. The form of file access permitted for a user or process.
ACL. See automatic cartridge loader (ACL).
ACS. See automated cartridge subsystem (ACS).
action. An operation that can be performed on a selected resource.
activation. The operator action of putting software into use after the software has been
applied from the activation package to the target system.
activation package. A set of files containing product files, operator instructions, and
instructions for applying the software on the target system. It consists of a header file
containing the activation instructions and file attributes, multiple data files, Distributed
Systems Management/Software Configuration Manager (DSM/SCM) control
information, and Event Management Service (EMS) events.
AC transfer switch. A component of an HP NonStop™ Cluster Switch (model 6770) that
provides access to dual AC power sources and the ability to switch between the two
sources if one fails. The AC transfer switch draws power from its primary power source
as long as it is available. If the primary source fails, the AC transfer switch is switched
to draw power from the secondary power source.
adapter. See ServerNet adapter.
adapter cable. (1) A cable that connects components that have incompatible electrical
interfaces. (2) For the ServerNet wide area network (SWAN) concentrator, one of four