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-69
open propagation
open propagation. In the Open System Services (OSS) file system, the set of events and
outcomes that occur when an open file description is inherited by a child process in the
same processor as its parent process. Contrast with open migration
.
Open SCSI. A subsystem that provides the hardware and software for a SCSI-2 open
interface that runs on HP NonStop™ S-series servers and to which developers can
attach small computer system interface (SCSI)
devices.
open system. A system with interfaces that conform to international computing standards
and therefore appear the same regardless of the system’s manufacturer. For example,
the Open System Services (OSS) environment on HP NonStop™ systems conforms to
international standards such as ISO/IEC IS 9945-1:1990 (ANSI/IEEE Std. 1003.1-
1990, also known as POSIX.1), national standards such as FIPS 151-2, and portions
of industry specifications such as the X/Open Portability Guide Version 4 (XPG4).
Open System Services (OSS). An open system environment available for interactive or
programmatic use with the HP NonStop™ Kernel operating system. Processes that run
in the OSS environment usually use the OSS application program interface. Interactive
users of the OSS environment usually use the OSS shell for their command interpreter.
Synonymous with
Open System Services (OSS) environment. Contrast with Guardian.
Open System Services (OSS) environment. The HP NonStop™ Kernel Open System
Services (OSS) application program interface (API), tools, and utilities.
Open System Services (OSS) Monitor. A Guardian utility that accepts commands affecting
OSS objects through an interactive Guardian interface named the Subsystem Control
Facility (SCF).
Open System Services (OSS) signal. A signal model defined in the POSIX.1 specification
and available to TNS processes and TNS/R native processes in the OSS environment.
OSS signals can be sent between processes.
Open Systems Interconnection (OSI). A seven-layer network architecture model defined
by the International Organization for Standardization (ISO). The two lowest layers deal
with the physical connections and their protocols. The five upper layers deal with
network services, such as network file transfers and access to remote databases.
Open Systems Interconnection Layer 2. The data-link control level of the Open Systems
Interconnection (OSI) model, composed of asynchronous or minimal line control
protocols, byte-oriented or character-oriented protocols, and bit-synchronous or
bit-oriented protocols. Data link protocols can be defined in terms of method of access
of data, link relationship of stations, error detection scheme, error recovery, message
formatting, logical half-duplex or full-duplex operation, code, and machine
transparency.
operating system image. See OSIMAGE.