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-32
Expand-over-ServerNet line-handler process
device number as its Expand-over-ServerNet line-handler process. However, the line
does not have the same states as the line-handler process.
Expand-over-ServerNet line-handler process. An Expand line-handler process that uses
the NETNAM protocol to access the Network Access Method (NAM) interface provided
by the ServerNet cluster monitor process, $ZZSCL. The Expand-over-ServerNet line-
handler process handles incoming and outgoing Expand messages. It also handles
packets leaving the server and security-related messages going between systems
within a ServerNet cluster. Each node in a ServerNet cluster must be configured with
an Expand-over-ServerNet line-handler process for every other node in the ServerNet
cluster.
expansion service processor (ESP). A service processor (SP) that is not a master service
processor (MSP). ESPs occur in pairs in groups 02 through
nn (not in group 01). See
also master service processor (MSP)
.
explicit DLL. See explicit dynamic-link library (explicit DLL).
explicit dynamic-link library (explicit DLL). A dynamic-link library (DLL) that is named in
the libList of a client or is a native-compiled loadfile associated with a client.
export. To offer a symbol definition for use by other loadfiles. A loadfile exports a symbol
definition for use by other loadfiles that need a data item or function having that
symbolic name.
export digest. A mathematical hash of the exported symbol names and locations in a
library. Two libraries with the same export digest are interchangeable in that they both
export the same symbols at the same locations. They are not necessarily semantically
equivalent.
extended data segment. See selectable segment.
extended link format (ELF). A standard binary file format common on UNIX systems. The
ELF format is used for position-independent code (PIC) files.
extensible input/output (XIO). A redesign of the HP NonStop™ Kernel operating system’s
I/O subsystem to enable it to extend itself in general ways to meet future requirements.
extent. A contiguous area on disk for allocating one file.
extent size. The size in bytes of a contiguous area on disk for allocating one file.
external entry point (XEP) table. A table located in the last page of each TNS code
segment that contains links for calls (unresolved external references) out of that
segment.
external fabric connection. The low-level ServerNet connection between a node and one
of the external ServerNet fabrics. Each node has an X and a Y connection to the
external fabrics.