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-11
CE
CE. Customer engineer. See service provider.
cell. See storage pool.
central processing unit (CPU). Historically, the main data processing unit of a computer.
The HP NonStop™ servers have multiple cooperating processors rather than a single
CPU. See also processor
.
Challenge Handshake Authentication Protocol (CHAP). An Internet-standard protocol for
verifying encrypted passwords. CHAP is a security protocol that is implemented using
Point-to-Point Protocol (PPP)
. The OSM and TSM Notification Director use CHAP to
maintain security during dial-outs.
channel. An information route for data transmission. See also ServerNet link.
CHAP. See Challenge Handshake Authentication Protocol (CHAP).
character. A sequence of one or more bytes representing a single character; used for the
organization, representation, or control of data. A single-byte character consists of
eight bits that represent a character. A multibyte character uses one or more bytes to
represent a character. A wide character is a fixed-width character wide enough to hold
any coded character supported by an implementation.
The ISO C standard defines the term multibyte character; a single-byte character is a
special case of multibyte character.
character set. A finite set of characters (letters, digits, symbols, ideographs, or control
functions) used for the organization, representation, or control of data. See also code
set.
character special file. In the Open System Services (OSS) environment, a device that is
treated as a file for which all input or output must occur in character bytes. Traditionally,
such files are interactive terminals, and the ISO/IEC IS 9945-1:1990 standard defines
only the access to such terminal files. See also terminal
. Contrast with block special
file.
chassis. A single sheet-metal structure that houses one set of system components. In an
HP NonStop S-series server, a chassis is part of a system enclosure but can also be
mounted in any standard 19-inch rack.
checksum. A generic term, meaning to add together (although the definition of add need
not be a normal arithmetic add) all of the data to produce a check
word. See also cyclic
redundancy check (CRC).
child process. A process created by another process. The creating process becomes the
parent process of the new process. See also parent process
.