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-14
CMI
CMI. See Communications Management Interface (CMI).
code segment. A segment that contains executable instructions of a program or library to
be executed plus related information. Code segments can be executed and also
accessed as read-only data but not written to by an application program. These read-
only and execute-only segments are efficiently shared among simultaneous executions
of that program or library. Therefore, they are read from disk but are never written back
to disk. See also
TNS code space.
code set. Codes that map a unique numeric value to each character in a character set,
using a designated number of bits to represent each character. Single-byte code sets
use 7 or 8 bits to represent each character. The ASCII and ISO 646 code sets use 7
bits to represent each character in Roman-based alphabets; these code sets are very
limited and are not appropriate for international use. The single-byte ISO 8859 code
sets use 8 bits to represent each character and can therefore support Roman-based
alphabets and many others including Greek, Arabic, Hebrew, and Turkish. Multibyte
code sets represent characters that require more than one byte, such as East Asian
ideographic characters.
code space. See TNS code space.
cold load. A synonym for system load or load (in the case of single processor load). System
load or load is the preferred term in HP NonStop™ S-series system publications.
command. A demand for action by or information from a subsystem or the operation
demanded by an operator or application. A command is typically conveyed as an
interprocess message from an application to a subsystem.
command file. An EDIT file that contains a series of commands and serves as a source of
command input.
common applications environment (CAE). A computer environment in which applications
can be ported across all X/Open branded products because of the use of international
and industry standards. A CAE is an open system application development
environment, an open system execution environment, or a combination of the two.
common base board (CBB). In modular customer-replaceable units (CRUs), the printed
wiring assembly (PWA) that plug-in cards (PICs) are installed in.
Common Communication ServerNet adapter (CCSA). A ServerNet adapter that provides
an HP NonStop™ S-series integration platform for Signaling System Number 7 (SS7)
protocol communications.
common mode. Electrical interference that can be measured as a ground-referenced
signal. In true common mode, a signal is common to all of the current-carrying
conductors.
common-mode transients. Transients that appear between both inputs of a circuit and a
common reference (such as ground).