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-76
POOL object type
information over point-to-point links. OSM and TSM use PPP to provide TCP/IP
communication over a dial-up connection.
POOL object type. The Subsystem Control Facility (SCF) object type for storage pool
storage pools.
port. (1) A data channel that connects to other devices or computers. (2) A connector to
which a cable can be attached. The system transmits and receives data or requests
through ports on ServerNet adapters and processor multifunction (PMF) customer-
replaceable units (CRUs). A port is also called a connector. (3) The entrance or
physical access point (such as a connector) to a computer, multiplexer, device, or
network where signals are supplied, extracted, or observed.
portable application. An application that can execute on a wide range of hardware
systems from multiple manufacturers. A portable application is a program that can be
moved with little or no change in its source code from another manufacturer’s system
to an HP NonStop™ system.
portable filename character set. The set of characters that includes the Roman uppercase
and lowercase letters, the Arabic numerals, the period, the underscore, and the
hyphen. The hyphen cannot be the first character of a portable filename.
portable pathname character set. The set of characters that includes the Roman
uppercase and lowercase letters, the Arabic numerals, the period, the underscore, the
slash (
/), and the hyphen. The hyphen cannot be the first character of a portable
pathname.
Portable Silicon Operating System (pSOS) system product. A product of Integrated
Systems Inc. that provides support for industry-standard communications protocols
based on the UNIX operating system. It is used as a compact multitasking kernel
operating system for PowerPCs and similar systems.
position ID. A character that indicates the position an HP NonStop™ Cluster Switch
occupies in a network topology. The position ID is a component of the two-character
cluster switch name. The cluster switch name includes an external fabric ID (X or Y) as
the first character and a position ID as the second character. For example, the cluster
switch name X3 indicates that the cluster switch serves the external ServerNet X fabric
and occupies position 3 in the topology. Supported values for position IDs are 1
through 9 or A through Z. Currently supported topologies (star, split-star, and tri-star)
use position IDs 1, 2, and 3.
position-independent code (PIC). Executable program or library code that is designed to
be loaded and executed at any virtual memory address, without any modification.
Addresses that can be modified by the loader do not appear in PIC code, only in data
that can be modified by the loader. See also dynamic-link library (DLL)
.