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-110
three point fall of potential measurement method
three point fall of potential measurement method. The measurement of a grounding
electrode (such as a ground rod) where ground resistance is measured with respect to
two other points. The ratio of the measurements determines the resistance of the
grounding electrode.
TIM. See HP NonStop™ Technical Library (NTL).
time factor (TF). A number assigned to a line, path, or route to indicate its efficiency in
transporting data. The lower the time factor, the more efficient the line, path, or route.
See also surge
.
TLB. See translation lookaside buffer (TLB).
TMF. See HP NonStop™ Transaction Management Facility (TMF).
TNS. HP computers that support the HP NonStop™ Kernel operating system and that are
based on complex instruction-set computing (CISC) technology. TNS processors
implement the TNS instruction set. Contrast with TNS/R
.
TNS code segment index. A value in the range 0 through 31 that indexes a code segment
within the current user code, user library, system code, or system library space. This
value can be encoded in five bits.
TNS code space. One of four addressable collections of TNS object code in a TNS
process. They are User Code (UC), User Library (UL), System Code (SC), and System
Library (SL). UC and UL exist on a per-process basis. SC and SL exist on a per-node
basis.
TNS instructions. Stack-oriented, 16-bit machine instructions defined as part of the TNS
environment. On TNS systems, TNS instructions are implemented by microcode. On
TNS/R systems, TNS instructions are implemented by millicode routines or by
translation to an equivalent sequence of RISC instructions.
TNS library. A single, optional, TNS-compiled loadfile associated with one or more
application loadfiles. If a user library has its own global or static variables, it is called a
TNS shared run-time library (TNS SRL). Otherwise it is called a User Library (UL).
TNS loading. A task performed at process startup time when executing a TNS object file.
This task involves mapping the TNS instructions, procedure entry point (PEP) table,
and external entry point (XEP) table from a TNS object file into memory.
TNS mode. The operational environment in which TNS instructions execute by inline
interpretation. See also accelerated mode
and TNS/R native mode.
TNS object code. The TNS instructions that result from processing program source code
with a TNS language compiler. TNS object code executes on both TNS and TNS/R
systems.