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-43
hard link
server version T7945AAX (shipped with G06.13) or later, use the appropriate guided
procedure.
hard link. In the Open System Services (OSS) file system, the relationship between two
directory entries for the same file. A hard link acts as an additional pointer to a file. A
hard link cannot be used to point to a file in another fileset. Contrast with symbolic link
.
hard reset. An action performed on an HP NonStop™ Cluster Switch (model 6770) and HP
NonStop™ ServerNet Switch (model 6780) that reinitializes the router-2 ASIC within
the switch, disrupting the routing of ServerNet messages through the switch for several
minutes. When the hard reset is finished, the paths are restored automatically.
harmonic. The sinusoidal component of an alternating-current (AC) voltage that is a
multiple of the waveform frequency.
harmonic distortion. Harmonics that change an alternating-current (AC) waveform from
sinusoidal to complex.
header. An object that, when specified for inclusion in a program’s source code, causes the
program to behave as if the statement including the header were actually a specific set
of other programming statements. A header contains coded information that provides
details (such as data item length) about the data that the header precedes.
In an Open System Services (OSS) program, a header is the name of a file known to
the run-time library used by a process. In a Guardian environment C language
program, a header is the file identifier for a file known to the run-time library used by a
process.
hertz (Hz). A unit of frequency. One hertz equals one cycle/second.
high frequency. A Federal Communications Commission (FCC) designation for a
frequency in the range 30 through 300 megahertz, corresponding to a decametric
wave in the range 10 through 100 meters.
high PIN. A process identification number (PIN) that is greater than 255. Contrast with low
PIN.
hop count. The number of routers that form a route between a ServerNet source and
ServerNet destination. Hop count is used to determine the best route. If two alternate
routes have the same time factor, the path with the lower hop count is the better route.
host database. An SQL database maintained for the host system and containing
information about requests, software inputs, snapshots, targets, and profiles.
host system. (1) A computer system that supports very large databases and does batch
processing, usually for an entire network of smaller systems. (2) The central site on
which the Distributed Systems Management/Software Configuration Manager
(DSM/SCM) is managed, the Archive is maintained, and configuration revisions are
built. The host system is also a target system.