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-84
remote interprocessor communication (RIPC)
console and access your HP NonStop™ S-series server to diagnose hardware and
software problems. See also remote notification
.
remote interprocessor communication (RIPC). The exchange of messages between
processors in different systems or nodes.
remote mount. A mount used by a Network File System (NFS) client to attach part of the
local NFS file hierarchy to a point within the client’s remote file hierarchy. The remote
mount is visible only to the NFS client performing the mount. In effect, the local
hierarchy from the mount point down is exported to the client performing the remote
mount.
remote node. See remote system.
remote notification. A form of remote support. Remote notification, or dial-out, allows the
OSM or TSM Notification Director to notify a service provider, such as the Global
Customer Support Center (GCSC), of pending hardware and software problems. See
also remote access
.
remote operator. The person who performs routine system operations from a geographical
distance, usually when no local operator is present.
remote procedure. A procedure or function packaged to be called within a server process
indirectly by a client process.
remote procedure call. A remote procedure or the action of calling a remote procedure.
Remote Procedure Call (RPC). A protocol that extends a procedure-call form of process-
to-process communication to a network environment. RPC is a way for programs
running on client computers to invoke the services of a program running on a server
computer. RPC allows a program to call a procedure that does not exist on the client
computer.
remote procedure call system. A set of facilities that includes a programming library,
network resource mapping, and binding services to provide a mechanism for a client
process to execute a procedure on a remote server. A remote procedure call system is
a subset of the Distributed Computing Environment (DCE) and of other products.
remote processor. A processor in a node other than the node running the ServerNet
cluster monitor process (SNETMON) that is reporting status about the processor.
remote switch. An HP NonStop Cluster Switch (model 6770) or HP NonStop ServerNet
Switch (model 6780) in a ServerNet cluster that is not directly connected to the server
that you are logged on to. The OSM Service Connection and the TSM Service
Application cannot perform any actions on a remote switch. To perform actions or get
additional information on a remote switch, use the OSM Service Connection (for either
the 6770 or 6780 switch) or TSM Service Application (for the 6770 switch only) to log
on to a server that is directly connected to the switch.