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-70
operational environment
operational environment. The conditions under which your system performs. These
conditions include the devices and communications lines that are made active and the
system and application processes that are started at system startup.
operator. (1) A symbol, such as an arithmetic or conditional operator, that performs a
specific operation on operands. (2) In Network Control Language (NCL), a lexical
element used for working on terms in expressions. The five types of operators are
parenthetical, arithmetic, Boolean, relational, and string. (3) For an HP NonStop™
system, the person or program responsible for day-to-day monitoring and maintenance
tasks associated with the HP NonStop Kernel operating system and the hardware of a
NonStop node. The operator issues commands to subsystems; retrieves, examines,
and responds to event messages; or does any combination of those things. See also
local operator
. Contrast with administrator. (4) For a UNIX system, any interactive user
of that system.
operator message. A message, intended for an operator, that describes a significant event
on an HP NonStop™ S-series system. An operator message is the displayed-text form
of an Event Management Service (EMS) event message
.
option. In a UNIX or Open System Services (OSS) command, a flag and its parameters or
a flag without parameters.
ordinary library. A dynamic-link library (DLL) or shared run-time library (SRL) that is not
public. See ordinary dynamic-link library (ordinary DLL)
.
ordinary dynamic-link library (ordinary DLL). A dynamic-link library (DLL) or shared
run-time library (SRL) that is not public. The code file is found at run time and can be
provided by the user. Contrast with public dynamic-link library (public DLL)
.
orphaned process group. In the Open System Services (OSS) environment, a process
group in which the parent of every member is also either a member of the process
group or a member of a different session.
orphan file. In the Open System Services (OSS) environment, a file with no corresponding
inode in the PXINODE file.
orphan inode. In the Open System Services (OSS) environment, an inode that appears in
the PXINODE file but has no links in the PXLINK file.
OSC. See Online Support Center (OSC).
OSCONFIG file. In G-series release version updates (RVUs), a configuration file built during
system generation that contains only Software Problem Isolation and Fix Facility
(SPIFF) and Software Identification (SWID) tool records. In D-series and earlier RVUs,
the Configuration Utility Program (COUP) uses the $SYSTEM.SYS
nn.OSCONFIG file
to store its configuration information.
OSI. See Open Systems Interconnection (OSI).