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-7
backout
backout. The Distributed Systems Management/Software Configuration Manager
(DSM/SCM) action of making the last configuration applied to the target system
inaccessible and replacing it with the previous configuration.
backplane. A board that has connectors, on one or both sides of the board, into which
circuit board assemblies plug. Backplanes are located behind card cages.
BACKUP. A utility for the HP NonStop™ servers that creates a backup copy of one or more
disk files on magnetic tape. See also RESTORE
.
backup processor. A processor running the HP NonStop™ Kernel operating system that
communicates with the primary processor
, allowing the processors to remain
independent. A component failure in one processor has no effect on any other
processor.
base computing platform. The minimum software implementation that is the foundation for
the X/Open common applications environment (CAE)
.
base enclosure. An enclosure that is placed on the floor and can have other enclosures
stacked on top of it. A base enclosure is installed on a frame base. Contrast with
stackable enclosure
.
base profile. In an X/Open compliant system, a minimum set of software components
required to create a common applications environment.
battery load. The electrical current drain imposed on a battery.
BEB. See back-end board (BEB).
BIC. Backplane interconnect card. Not applicable to HP NonStop™ S-series servers. See
ServerNet adapter
.
BIND. A program invoked during system generation that creates TNS object (file code 100)
system code files and system library files.
Binder. A programming utility that combines one or more compilation units’ TNS object
code files to create an executable TNS object code file for a TNS program or library.
Used only with TNS object file
s.
Binder region. The region of a TNS object file that contains header tables for use by the
Binder program.
binding. The operation of collecting, connecting, and relocating code and data blocks from
one or more separately compiled TNS object files to produce a target object file.
bit-synchronous. A type of Open Systems Interconnection (OSI) Layer-2 protocol that uses
synchronous transmission but does not require a character code to define terminal and
line control sequences.