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-54
KB
KB. See kilobyte (KB).
Kernel subsystem. In G-series release version updates (RVUs), the subsystem for
configuration and management of the Subsystem Control Facility (SCF) subsystem
managers that are generic processes, some system attributes, and the ServerNet X
and Y fabrics.
Kernel subsystem manager process. The generic process that starts and manages other
generic processes, some system attributes, and the ServerNet X and Y fabrics in
G-series release version updates (RVUs). The $ZZKRN Kernel subsystem manager
process is started and managed by the $ZPM persistence manager process.
kilobyte (KB). A unit of measurement equal to 1024 bytes. See also gigabyte (GB),
megabyte (MB)
, and terabyte (TB).
K-series servers. See HP NonStop™ K-series servers.
L10N. See localization.
labeled dump. A token-by-token display-text representation of the Subsystem
Programmatic Interface (SPI) command buffer or response buffer, as produced by the
Subsystem Control Facility (SCF) commands DETAIL CMDBUFFER and DETAIL
RSPBUFFER. The display text includes a labeled value for each token.
LAN. See local area network (LAN).
LANMAN. See LAN manager (LANMAN) process.
LAN manager (LANMAN) process. The process provided as part of the ServerNet local
area network (LAN) Systems Access (SLSA) subsystem that starts and manages the
SLSA subsystem objects and the LAN monitor (LANMON) process and assigns
ownership of Ethernet adapters to the LANMON processes in the system. Subsystem
Control Facility (SCF) commands are directed to the LANMON processes for
configuring and managing the SLSA subsystem and the Ethernet adapters.
LANMON. See LAN monitor (LANMON) process.
LAN monitor (LANMON) process. The process provided as part of the ServerNet local
area network (LAN) Systems Access (SLSA) subsystem that has ownership of the
Ethernet adapters controlled by the SLSA subsystem.
late binding. At load time, binding a symbolic reference in a dynamic-link library (DLL) to a
definition in a loadfile that appears on the program’s loadList rather than the one found
on the DLL’s linker searchList. Late binding occurs in either of these cases:
•
The loader resolves a symbol that is unresolved by any loadfile on the linker
searchList.