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-58
localization
localization. The process of adapting computer interfaces, data, and documentation to the
culturally accepted way of presenting information in the culture. Sometimes referred to
as
L10N, derived from the 10 letters between the initial L and the final N of the word
localization.
localized. The import-control characteristic of a loadfile that allows it to import symbols only
from the loadfile itself followed by the libraries in its libList, libraries that those libraries
reexport, and from these, any successions of reexported libraries. See also register-
exact point and searchList.
local mount. In the Network File System (NFS), a mount that attaches the fileset
associated with a server to the specified mount point within the local directory
hierarchy. The local mount is visible within the NFS subsystem and makes the files
associated with the server available through the path associated with the local mount
point.
local node. See local system.
local operator. The person who performs routine system operations, such as starting and
stopping the system, loading and unloading tapes, and changing the air filter. The local
operator is normally the operator of the asynchronous system console for the node.
See also operator
.
local processor. A processor in the same node as the ServerNet cluster monitor process
(SNETMON) that is reporting status about the processor.
local system. (1) An on-site system or a system that is geographically near the user or
operator. (2) From the perspective of a particular SNETMON, the system or node on
which that SNETMON is running. (3) From the perspective of a system console
operator, the system to which the operator is logged on. Contrast with remote system
.
logical device name. The name assigned to an I/O process during its configuration. Other
processes use the logical device name when issuing Guardian procedure calls to the
I/O process.
logical device number (ldev). For a device or named process, the index into the
destination control table (DCT)
; or more precisely, into the named resource list (NRL).
Each device or named process in the system has an ldev.
logical disk volume. A hardware device or device pair that provides persistent, highly
accessible storage for data on a medium that is either magnetic or optical.
logical interface (LIF). A process that allows an application or another process to
communicate with data communications hardware.
logical memory unit (LMU). A group of four memory units. Memory on a processor and
memory board (PMB) is divided into two LMUs. One LMU contains memory units in
slots MS1 through MS4. The other LMU contains memory units in slots MS5 through