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-49
incremental discovery
incremental discovery. Discovery of an HP NonStop™ S-series server when the OSM or
TSM client software has locally saved information but where configuration changes
have been made on the server since that information was saved.
indicator lights. Two light-emitting diodes (LEDs) on a customer-replaceable unit (CRU)
that indicate the status of the unit. The red or amber indicator light is lit when the unit is
not working properly. During startup, this light can indicate that the unit is not yet
functioning. The green indicator light is lit when the unit has proper power applied. See
also light-emitting diode (LED)
.
inductive reactance. Resistance at a frequency that is caused by the inductance of a coil
or circuit.
initial discovery. Discovery of an HP NonStop™ S-series server with which the OSM or
TSM client software has had no prior contact and for which the client software has no
locally saved information.
initialization. The process of defining a new Distributed Systems Management/Software
Configuration Manager (DSM/SCM) target system, including giving it a name, setting
up default values used when processing requests, and creating the first software
revision (list of products) for the system.
initial software revision. The software revision on a target system when it is first brought
into the Distributed Systems Management/Software Configuration Manager
(DSM/SCM) environment. The DSM/SCM host database must be initialized with
information about the initial software revision. The initial software revision is then used
as a baseline upon which new software revisions are based.
inode. A data structure that stores the location of an Open System Services (OSS) file.
inode number. A unique identifier within the Open System Services (OSS) file system of an
instance of an OSS file. The inode number identifies the instance within the file system
catalogs.
input/output process (IOP). A running program (part of the HP NonStop™ Kernel
operating system) that manages the I/O functions for one or more ServerNet
addressable controllers (SACs) of the same type.
input source. The resource from which Subsystem Control Facility (SCF) accepts
command input. SCF can accept input from a terminal or a disk file. The initial input
source is determined by the form of the RUN command used to initiate SCF. At any
time during an SCF session, the input source can be temporarily changed to execute a
series of commands from a command file.
inrush current. The initial surge current demand of a load.
Inspect region. The region of a TNS object file that contains symbol tables for all blocks
compiled with the SYMBOLS directive. The Inspect region is sometimes called the
symbols region
.