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-85
remote system
remote system. An active ServerNet node to which the local system has active external
ServerNet paths. Contrast with local system
.
request packet. A ServerNet packet sent from one ServerNet device to another, requesting
either a read action or a write action on the part of the receiving device. In the case of
a write request, the packet contains the data to be written. The receiving device is
expected to take the appropriate action and return a response packet to the device that
sent the request packet. See also response packet
, ServerNet packet, and ServerNet
transaction.
reserved symbol. An identifier that is reserved for use by system or compiler language
implementors.
resistance. The measure of opposition to current that limits the amount of current that can
be produced by an applied voltage. Conductors have very little resistance; insulators
have a large amount of resistance. Resistance is measured in ohms.
resource. A component of a computer system that works with other components to process
transactions. Terminals, workstations, processors, memory, disk drives, processes,
files, and applications are examples of resources.
response. The information or confirmation supplied by a subsystem in reaction to a
command. A response is typically conveyed as one or more interprocess messages
from a subsystem to an application.
response packet. A ServerNet packet returned from one ServerNet device to another,
responding to an earlier received read request or write request. In the case of
responding to a read request, the response packet contains the data that the
requesting device wanted to have read. See also request packet
, ServerNet packet,
and ServerNet transaction
.
RESTORE. A utility for HP NonStop™ servers that copies files from a backup tape to disk.
See also BACKUP
.
RFC. Request for Comments. Documents compiled by number by the Internet Engineering
Task Force (IETF) that define standards for intercommunication.
RFI. See radio frequency interference (RFI).
RIPC. See remote interprocessor communication (RIPC).
RISC. See reduced instruction-set computing (RISC).
RISC processor. An instruction processing unit (IPU) that is based on reduced
instruction-set computing (RISC) architecture. TNS/R processors contain RISC
processors.