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-12
CIIN
CIIN. A command file in the SYSnn subvolume that is read and executed by the startup HP
Tandem Advanced Command Language (TACL) process after system load if the CIIN
file is specified in the CONFTEXT file and enabled in the OSM or TSM Low-Level Link.
circuit breaker. A device designed to open and close a circuit by nonautomatic means and
to open the circuit automatically on a predetermined overcurrent without damage to
itself.
CISC. See complex instruction-set computing (CISC).
CISC processor. An instruction processing unit (IPU) that is based on complex
instruction-set computing (CISC) architecture.
class. A group of object-oriented data entities and the methods associated with that group.
Class-1 CRU. A customer-replaceable unit (CRU) that probably will not cause a partial or
total system outage if the documented replacement procedure is not followed correctly.
Customers replacing Class-1 CRUs are not required to have previous experience
replacing HP NonStop™ S-series CRUs. However, for some CRUs, customers must
be able to use the tools needed for the replacement procedure (which are common
tools) and must protect components from electrostatic discharge (ESD).
Class-2 CRU. A customer-replaceable unit (CRU) that might cause a partial or total system
outage if the documented replacement procedure is not followed correctly. Customers
replacing Class-2 CRUs should have either three or more months of experience
replacing HP NonStop™ S-series CRUs or equivalent training. Customers must be
able to use the tools needed for the replacement procedure and must protect
components from electrostatic discharge (ESD).
Class-3 CRU. A customer-replaceable unit (CRU) that probably will cause a partial or total
system outage if the documented replacement procedure is not followed correctly.
Customers replacing Class-3 CRUs should have either six or more months of
experience replacing HP NonStop™ S-series CRUs or equivalent training. Customers
must be able to use the tools needed for the replacement procedure, must protect
components from electrostatic discharge (ESD), and must understand the
dependencies involved in NonStop S-series CRU-replacement procedures, such as
disk-path switching. Replacement by a service provider trained by HP is
recommended.
client. A software process, hardware device, or combination of the two that requests
services from a server. Often, the client is a process residing on a programmable
workstation and is the part of an application that provides the user interface. The
workstation client might also perform other portions of the application logic.
client application. An application that requests a service from a server application.
Execution of remote procedure calls is an example of a client application.
client (of a loadable library). A loadfile that uses functions or data from a library.