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-56
LIC
system can also retain the bindings as modified when a loadfile is loaded and
associate a LIC with those cached bindings, so that they can be reused when the
same file is again loaded in an equivalent environment. (See
cached bindings.)
LIC. See library import characterization (LIC).
LIF. See logical interface (LIF).
light-emitting diode (LED). A semiconductor device that emits light from its surface.
Indicator lights are composed of LEDs. See also indicator lights
.
line. The specific hardware path over which data is transmitted or received. A line can also
have a process name associated with it that identifies an input/output process (IOP) or
logical device associated with that specific hardware path.
linear load. Electrical loads for which the impedance is constant regardless of the voltage,
so that if the voltage is sinusoidal, the current drawn is also sinusoidal.
line-handler process. See Expand line-handler process or Expand-over-ServerNet
line-handler process.
line interface unit (LIU). A dual-ported unit consisting of two parts: a communications line
interface processor (CLIP) and a line interface module (LIM). An LIU can communicate
with either the primary or the backup processor, providing fault tolerance. When it is a
component of the communications subsystem, an LIU communicates with either
processor through either of a pair of communications interface units (CIUs).
link. In the Open System Services (OSS) file system, a directory entry for a file.
link count. In the Open System Services (OSS) file system, the number of directory entries
that refer to a particular file.
linker. (1) The process or server that invokes the message system to deliver a message to
some other process or server. (2) A programming utility, which combines one or more
compilation units’ linkfiles to create an executable loadfile for a native program or
library.
linkfile. (1) For native C/C++ compilers in the Guardian environment, a command file for
input to the
nld or ld utility. (2) A file containing object code that is not yet ready to
load and execute. Linkfiles are combined by means of a linker or binder to make an
executable loadfile for a program or library. Compiling creates one linkfile per
independent source module. Contrast with loadfile
.
linking. The operation of collecting, connecting, and relocating code and data blocks from
one or more separately compiled object files to produce a target object file.
link name. In the Open System Services (OSS) environment, the filename associated with
a specific file within a directory. The length of a filename, and therefore the length of a
link name, depends on the file system.