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-113
Trivial File Transfer Protocol (TFTP)
G06.14 release version update (RVU), the tri-star topology supports up to 24 nodes.
See also split-star topology
, star topology, and layered topology.
Trivial File Transfer Protocol (TFTP). A protocol defined by Request for Comments (RFC)
1350. TFTP is used as a data link control (DLC) and diagnostic task.
TRSA. See Token-Ring ServerNet adapter (TRSA).
TSM. See Compaq TSM.
TSM client software. See Compaq TSM client software.
TSM Event Viewer. See Compaq TSM Event Viewer.
TSM Low-Level Link. See Compaq TSM Low-Level Link.
TSM Notification Director. A component of the Compaq TSM client software. The TSM
Notification Director receives incident reports from an HP NonStop™ S-series server,
displays them, and allows you to take action or forward the incident reports to your
service provider for resolution. The TSM Notification Director can be configured to run
on a system console at all times, even when other TSM applications are not being
used.
TSM package. See Compaq TSM package.
TSM server software. See Compaq TSM server software.
TSM Service Application. See Compaq TSM Service Application.
two-lane link. The two single-mode fiber-optic (SMF) ServerNet cables that connect the HP
NonStop™ Cluster Switches on the same external fabric (for example, X1, X2, and X3)
in a tri-star topology
.
UCME. See uncorrectable memory error (UCME).
UID. A nonnegative integer that uniquely identifies a user within a node.
In the Open System Services (OSS) environment, the UID is the scalar view of the HP
NonStop™ Kernel user ID. The UID is used in the OSS environment for functions
normally associated with a UNIX user ID.
unattended site. A computer environment where no operator resides on site and the only
access is from a central monitoring station.
uncorrectable memory error (UCME). An error caused by incorrect data at a particular
memory location. The cause of the error is such that the error is not automatically
corrected by the system, and memory replacement is required. Contrast with
correctable memory error (CME)
.