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-21
customer-installable system
customer-installable system. A system that does not require specially trained service
providers to install.
customer-replaceable unit (CRU). A unit that can be replaced in the field either by
customers or by qualified personnel trained by HP. CRUs are divided into the
categories of Class 1, Class 2, and Class 3 based on the risk of causing a system
outage if the documented replacement procedure is not followed correctly and how
much CRU-replacement training or experience is advisable. See also Class-1 CRU
,
Class-2 CRU
, Class-3 CRU, and field-replaceable unit (FRU).
cyclic redundancy check (CRC). The most widely used error detection code for ensuring
the integrity of transmitted data. The digits of the CRC are calculated by the sender for
each block of data sent and recalculated by the receiver. (It is a family of mathematical
functions involving computing the quotient and remainder of a polynomial division.) A
CRC is a form of checksum
.
daemon. See demon.
dark site. See unattended site.
data communications equipment (DCE). Equipment that provides all the functions
required to establish, maintain, and terminate a connection and provides the signal
conversion and coding between the data terminal equipment (DTE) and telephone
company lines or data circuits. A DCE is usually a modem.
data link control (DLC). A set of functions associated with Layer 2 of the Open Systems
Interconnection (OSI) reference model. These functions are responsible for reliable
communication between two physically connected nodes.
data link control (DLC) task. Tasks that support the equivalent to Layer 2 of the Open
Systems Interconnection (OSI) reference model. Wide area network (WAN) DLC tasks
execute in the ServerNet wide area network (SWAN) concentrator communications line
interface processor (CLIP), and each WAN DLC task controls one line interface.
data segment. A virtual memory segment holding data. Every process begins with its own
data segments for program global variables and runtime stacks (and for some libraries,
instance data). Additional data segments can be dynamically created. See also flat
segment and selectable segment.
data terminal equipment (DTE). Equipment that constitutes the data source or data sink
and provides for the communication control function protocol. It includes any piece of
equipment at which a communication path begins or ends.
data transparent. Describes software that examines all eight bits of every data byte and
that uses no bit in a data byte for its own purposes. Internationalized applications must
be data transparent.
dB. See decibel (dB).