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-26
downward compatibility
downward compatibility. The ability of a requester to operate with a server of an earlier
revision level. In this case, the requester is downward-compatible with the server, and
the server is upward-compatible with the requester. Contrast with upward compatibility
.
drive. See disk drive or tape drive.
dropout. A voltage loss of very short duration (that is, milliseconds).
DSC. See Dynamic System Configuration (DSC).
DSM. See Distributed Systems Management (DSM).
DSM/SCM. See Distributed Systems Management/Software Configuration Manager
(DSM/SCM).
DSV. See distribution subvolume (DSV).
DTE. See data terminal equipment (DTE).
dual inline memory module (DIMM). Small circuit boards carrying memory integrated
circuits, with signal and power pins on both sides of the board. A DIMM is different
from a single inline memory module (SIMM) in that the connections on each side of the
module connect to different chips, whereas the connections on both sides of a SIMM
connect to the same memory chip. This difference gives the DIMM a wider data path,
as more modules can be accessed at once.
dual-ported. The capability of a ServerNet adapter or peripheral device to receive data and
commands from two sources although only one source might have access at any
particular moment.
duplicate file descriptor. In the Open System Services (OSS) file system, a file descriptor
that refers to the same open file description as another file descriptor.
dynamic configuration file (DCF). An attachment file that is produced by the OSM and
TSM client software and accompanied by an incident report. The DCF contains a
snapshot of the system configuration, the state of the HP NonStop™ S-series server,
and outstanding alarms at the time that the incident report was issued. The DCF is
used by the service provider to avoid having to perform online discovery of the server
over dial-up telephone lines.
Dynamic Host Configuration Protocol (DHCP). An Internet protocol for automating the
configuration of computers that use TCP/IP. DHCP can automatically assign IP
addresses, deliver TCP/IP stack configuration parameters such as the subnet mask
and default router, and provide other configuration information such as the addresses
for printer, time, and news servers.
dynamic information. Information that represents the set of resources that actually exist in
the current configuration of an HP NonStop™ S-series server. Dynamic information is