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-72
packet
packet. A block of information that contains fields for addressing, sequencing information,
possible priority indicators, and a portion of a message or an entire message. See also
ServerNet packet
.
page. See memory page.
Parallel Library TCP/IP. An HP product that provides increased performance and scalability
over conventional Transmission Control Protocol/Internet Protocol (TCP/IP). Parallel
Library TCP/IP coexists with conventional TCP/IP on HP NonStop™ S-series systems
and supports Ethernet 4 ServerNet adapters (E4SAs), Fast Ethernet ServerNet
adapters (FESAs), Gigabit Ethernet ServerNet adapters (GESAs), and ServerNet wide
area network (SWAN) concentrators. See also HP NonStop™ TCP/IP
.
PARAM. An HP Tandem Advanced Command Language (TACL) command and a
Subsystem Control Facility (SCF) command you can use to create a parameter and
give it a value. The TACL process stores the values of parameters assigned by the
PARAM command and sends the values to applications that request parameter values.
parent directory. A particular directory in the hierarchy of directories within a file system.
The parent directory for a directory contains an entry for that specific directory and is
identified in that directory as the directory immediately above it in the hierarchy. The
parent directory for a file contains an entry for that file.
parent process. The process that created a given process or (if the creating process has
stopped) a process that has inherited a given process. See also child process
.
parent process ID. In the Open System Services (OSS) environment, an attribute of a child
process determined by the parent process. The parent process ID is the OSS process
ID of the current parent process.
passthrough terminator. See SCSI passthrough terminator.
path. The route between a processor and a subsystem. If a subsystem is configured for
fault tolerance, it has a primary path (from the primary processor) and a backup path
(from the backup processor).
pathname. In the Open System Services (OSS) file system and Network File System
(NFS), the string of characters that uniquely identifies a file within its file system. A
pathname can be either relative or absolute. See also ISO/IEC IS 9945-1:1990
(ANSI/IEEE Std. 1003.1-1990 or POSIX.1), Clause 2.2.2.57.
pathname component. See filename.
pathname resolution. In the Open System Services (OSS) environment, the process of
associating a single file with a specified pathname.
pathname-variable limits. Limits that can vary within the Open System Services (OSS) file
hierarchy; that is, the limits on a pathname variable that can vary according to the
directory in which pathname resolution begins.