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-81
product module (PM)
product module (PM). The part of the Subsystem Control Facility (SCF) subsystem that is
responsible for subsystem-specific command processing.
profile. Default values used by the Distributed Systems Management/Software
Configuration Manager (DSM/SCM) when processing requests. The three types of
profiles are the Configuration Manager profile, the system profile, and the target profile.
PROFILE object type. The Subsystem Control Facility (SCF) object type for the storage
subsystem configuration profile.
program. See program file.
program file. An executable object code file containing a program’s main routine plus
related routines statically linked together and combined into the same object file. Other
routines shared with other programs might be located in separately loaded libraries. A
program file can be named on a RUN command; other code files cannot. See also
object code file
.
pSOS system product. See Portable Silicon Operating System (pSOS) system product.
public dynamic-link library (public DLL). Optional native-mode executable code modules
available to all native user processes. A public library that is specified in the public
library registry, supplied by HP or, optionally, a user. Contrast with ordinary
dynamic-link library (ordinary DLL).
public LAN. See nondedicated (public) LAN.
public library. A dynamic-link library (DLL) or shared run-time library (SRL) that is known to
the operating system, available for execution by any process or user, and is not an
implicit library.
public shared run-time library (public SRL). A TNS/R library supplied by HP.
PUP. See Peripheral Utility Program (PUP).
quad-integrated communications controller (QUICC). The Motorola MC68360 chip. For
HP NonStop™ S-series servers, the QUICC is used as the service processor (SP) and
is the main part of the ServerNet wide area network (SWAN) concentrator
communications line interface processor (CLIP).
quality power. The attributes and configuration of the power-distribution systems installed
within a facility that best serve the power needs of that facility’s electrical equipment
(for example, computer systems, air conditioning, and so on), providing the minimum
possible disruption to equipment operation.
QUICC. See quad-integrated communications controller (QUICC).
R1. See ServerNet router 1.