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-55
layer number
•
The loader binds a symbol in a DLL to the first definition it finds on the program’s
loadList, and this is not the first definition that was encountered on the linker
searchList.
For localized loadfiles, the linker and loader searchLists are the same, so late binding
does not occur.
layer number. See cluster switch layer number.
layered topology. The network topology for ServerNet clusters using the HP NonStop™
ServerNet Switch (model 6780). The layered topology can scale by adding cluster
switch layers or zones. The layered topology supports up to four layers and three
zones. See also star topology
, split-star topology, and tri-star topology.
LB. See logic board (LB).
LC-LC cable. A multimode fiber cable that connects an Fibre Channel ServerNet adapter
(FCSA) to a Fibre Channel storage device or a Fibre Channel switch (FC switch).
LC-SC cable. A multimode fiber cable that connects an modular ServerNet expansion
board (MSEB) to an I/O adapter module (IOAM) or a Fibre Channel switch (FC switch).
ldev. See logical device number (ldev).
LED. See light-emitting diode (LED).
legacy system. An operating system that is not open but from which applications must be
ported or users transferred.
libList. The list of libraries to be loaded along with a loadfile. When linking the loadfile, the
linker constructs the libList from the names of libraries specified in the linker’s
command stream. It stores the libList within the loadfile.
library. A generic term for a collection of routines useful in many programs. An object code
library can take the form of a linkfile to be physically included into client programs, it
can be an OSS archive file containing several linkable modules, it can be a loadfile, or
it can be a system-managed collection of preloaded routines. Source-code libraries fall
outside the scope of this glossary. See also dynamic-link library (DLL)
and shared run-
time library (SRL).
library client. A program or another library that uses routines or variables from that library.
library file. See library.
library import characterization (LIC). A list of the export digests and relocation offsets of
all the libraries used to resolve symbols in a loadfile. It allows the loader and operating
system to determine when a file is being loaded in an environment equivalent to that
found by the linker or to a previous load. (See
fastLoad.) A LIC is generated and stored
in the loadfile by the linker when a file is preset; it can be used in a subsequent load
step to determine whether the loadfile’s existing bindings can be reused. The operating