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-109
TCP
TCP. See Transmission Control Protocol (TCP).
TCP/IP. See Transmission Control Protocol/Internet Protocol (TCP/IP).
TEMPLI. The Event Management Service (EMS) template installation program that merges
template object files from specified subsystems and produces resident and nonresident
template files.
terabyte (TB). A unit of measurement equal to 1,099,511,627,776 bytes (1024 gigabytes).
See also gigabyte (GB)
, kilobyte (KB), and megabyte (MB).
terminal. A type of Open System Services (OSS) character special file that conforms to the
interface description in Clause 7 of ISO/IEC IS 9945-1:1990.
terminator. A resistor connected to a signal wire in a bus or network for the purpose of
impedance matching to prevent reflections. SCSI chains, Ethernet cables, and some
LocalTalk wiring configurations require terminators.
Tetra 8 topology. A tetrahedral topology of HP NonStop™ S-series servers that allows a
maximum of four processor enclosures (eight processors) and eight I/O enclosures.
Contrast with Tetra 16 topology
.
Tetra 16 topology. A tetrahedral topology of HP NonStop™ S-series servers that allows a
maximum of eight processor enclosures (16 processors). The maximum number of I/O
enclosures allowed by the Tetra 16 topology varies depending on the release version
update (RVU) and the server model. Contrast with Tetra 8 topology
.
tetrahedral topology. A topology of HP NonStop™ S-series servers in which the ServerNet
connections between the processor enclosures form a tetrahedron. See also
tetrahedron
and topology.
tetrahedron. A solid bounded by four triangular faces. In ServerNet context, a tetrahedron
is four processors interconnected by ServerNet links so as to form a conceptual
tetrahedron. Each processor therefore has a direct connection to the other three
processors. See tetrahedral topology
.
text string. A variable-length sequence of ASCII characters, defined in the CONFTEXT file,
that an identifier
represents. When Distributed Systems Management/Software
Configuration Manager (DSM/SCM) encounters an identifier, it substitutes the
associated text string for the identifier.
TF. See time factor (TF).
TFDS. See HP Tandem Failure Data System (TFDS).
TFTP. See Trivial File Transfer Protocol (TFTP).
THD. See total harmonic distortion (THD).