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-57
Linux
Linux. Linus Torvald’s version of the UNIX operating system. See also
http://www.linux.org.
listener. The process or server that is notified by the message system that a message from
some other process or server is being delivered.
LIU. See line interface unit (LIU).
LMU. See logical memory unit (LMU).
load. (1) To transfer the HP NonStop™ Kernel operating system image or a program from
disk into a computer’s memory so that the operating system or program can run. (2) To
insert a tape into a tape drive, which prepares it for a tape operation (read or write).
loadable library. A loadfile that offers functions and data to other loadfiles. In this manual,
dynamic-link libraries and hybrid shared run-time libraries are libraries. A library cannot
normally be invoked externally; for example, by a RUN command. Instead, it is invoked
by calls or data references from client loadfiles.
loader. A programming utility that transfers a program into memory so it can run. The
mechanism that brings loadfiles into memory for execution, maps them into virtual
address space, and resolves symbol references among them. Synonyms include
run-time loader and run-time linker. The loader for TNS and for TNS/R native programs
and libraries that are not position-independent code (PIC) is part of the operating
system. For PIC loadfiles, a loader called RLD works with the operating system to load
programs and libraries.
loadfile. An executable object code file that is ready for loading into memory and executing
on the computer. Loadfiles are further classified as executable programs (containing a
main routine at which to begin execution of that program) or executable libraries
(supplying routines or variables to multiple programs or separately loaded libraries). A
TNS code file might be both a loadfile and a linkfile. Native code files are never both.
Contrast with linkfile
.
loadList. A list of all the libraries that must be loaded for a given loadfile to execute. A
loadfile’s loadList includes all the libraries in the given loadfile’s libList plus all the
libraries in those loadfiles’ libLists, and so forth. It does not include the implicit libraries.
The loadList order is the sequence in which these loadfiles are to be loaded when they
are not already loaded by a previous operation. The loadList of the program includes
all the loadfiles present in the process, in the order they were loaded.
local area network (LAN). A network that is located in a small geographical area and
whose communications technology provides a high-bandwidth, low-cost medium to
which low-cost nodes can be connected. One or more LANs can be connected to the
system such that the LAN users can access the system as if their workstations were
connected directly to it. Contrast with wide area network (WAN)
.
locale. In localization, the definition of the subset of a user’s environment that depends on
language and cultural conventions.