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-87
run-time linker
run-time linker. See linker.
run-time loader. See loader.
RVU. See release version update (RVU).
S700 server. See HP NonStop™ S700 server.
S7000 server. See HP NonStop™ S7000 server.
S7400 server. See HP NonStop™ S7400 server.
S7600 server. See HP NonStop™ S7600 server.
S7800 server. See HP NonStop™ S7800 server.
S70000 server. See HP NonStop™ Sxx000 server.
S72000 server. See HP NonStop™ Sxx000 server.
S74000 server. See HP NonStop™ Sxx000 server.
S76000 server. See HP NonStop™ Sxx000 server.
S86000 server. See HP NonStop™ Sxx000 server.
Sxx000 server. See HP NonStop™ Sxx000 server.
S-series servers. See HP NonStop™ S-series servers.
SAC. See ServerNet addressable controller (SAC).
sag. A reduction in voltage, usually lasting from one cycle to a few seconds. Sags are
typically caused by fault clearing or by heavy load startups.
SAN. System area network. The preferred term is fabrics.
SANMAN. See external system area network manager process (SANMAN).
saveabend file. A file containing dump information needed by the system debugging tool on
a TNS or TNS/R system. In UNIX systems, such files are usually called core files or
core dump files. A saveabend file is a special case of a save file. See also save file
.
saved-set group ID. An Open System Services (OSS) process attribute that stores a group
ID so that the group ID can later be used as the effective group ID of the process.
saved-set user ID. An Open System Services (OSS) process attribute that stores a user ID
so that the user ID can later be used as the effective user ID of the process.