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-71
OSIMAGE
OSIMAGE. A file built during system generation that contains the complete image of the HP
NonStop™ Kernel operating system that runs in each processor in the system.
OSM. See HP NonStop™ Open System Management (OSM) Interface.
OSM Event Viewer. OSM replacement for the TSM Event Viewer.
OSM Low-Level Link. OSM replacement for the TSM Low-Level Link.
OSM Notification Director. OSM replacement for the TSM Notification Director.
OSM Service Connection. OSM replacement for the TSM Service Application.
OSS. See Open System Services (OSS).
OSS environment. See Open System Services (OSS) environment.
OSS Monitor. See Open System Services (OSS) Monitor.
OSS process ID. In the Open System Services (OSS) environment, the unique identifier
that identifies a process during the lifetime of the process and during the lifetime of the
process group of that process. See also PID
.
OSS signal. See Open System Services (OSS) signal.
OSS user ID. See HP NonStop™ Kernel user ID.
outage. Time during which a computer system is not capable of doing useful work. Outages
can be planned or unplanned. From the end user’s perspective, an outage is any time
an application being used is not available. See also planned outage
and unplanned
outage.
outage minutes. A metric for measuring outages that translates percentages into
minutes/year of downtime.
output destination. The resource to which Subsystem Control Facility (SCF) sends its
responses to commands. SCF can direct output to a disk file, an application process, a
terminal, or a printer. The initial output destination is determined by the form of the
RUN command used to initiate SCF. The output destination can be changed
dynamically during an SCF session.
owner. (1) In the case of a disk file, the user or program that created the file, or a user or
program to whom the creator has given the file with the File Utility Program (FUP)
GIVE command. (2) In the case of a process, the user or program that created the
process or, if the PROGID option was specified in the FUP SECURE command for the
code file, the user or program that owns the code file. (3) In the case of a token or
other definition, the subsystem that provided the definition. (4) In the case of a
subsystem, the company or organization that provides the subsystem, or the
8-character string identifying that company.