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-111
TNS object file
TNS object file. The object file created by a TNS compiler. The file contains TNS
instructions and other information needed to construct the code spaces and the initial
data for a TNS process.
TNS process. A process initiated by executing a TNS or accelerated object file. A TNS
process, whether accelerated or not, uses TNS register and stack conventions.
Contrast with TNS/R native process
.
TNS shared run-time library (TNS SRL). A shared run-time library (SRL) available to TNS
processes in the Open System Services (OSS) environment. A TNS process can have
only one TNS SRL. A TNS SRL is implemented as a special user library that allows
shared global data.
TNS signal. A signal model available to TNS processes in the Guardian environment.
TNS stack segment. See TNS user data segment.
TNS system library. A collection of HP-supplied TNS-compiled routines available to all
TNS processes. There is no per-program or per-process customization of this library.
All routines are immediately available to a new process. No dynamic loading of code or
creation of instance data segments is involved. See also native system library
.
TNS user data segment. In a TNS process, the segment at virtual address zero. Its length
is limited to 128 kilobytes. A TNS program's global variables, stack, and 16-bit heap
must fit within the first 64 kilobytes. See also compiler extended-data segment
.
TNS user library. A user library available to TNS processes in the Guardian environment.
TNS/R. HP computers that support the HP NonStop™ Kernel operating system and that are
based on reduced instruction-set computing (RISC) technology. TNS/R processors
implement the RISC instruction set and are upwardly compatible with the TNS
system-level architecture. Systems with these processors include most of the HP
NonStop™ servers. Contrast with TNS
.
TNS/R library. A TNS/R native-mode library. For a PIC-compiled application, TNS/R
libraries can be dynamic-link libraries (DLLs) or hybridized native shared runtime
libraries (SRLs). For an application that is not PIC compiled, TNS/R libraries can only
be native SRLs.
TNS/R native mode. The operational environment in which native-compiled RISC
instructions execute. See also accelerated mode
and TNS mode.
TNS/R native process. A process initiated by executing code that has been compiled
directly to RISC instructions rather than to TNS instructions. Such a process uses
RISC register and stack conventions and executes in TNS/R native mode
.
TNS/R native shared run-time library (TNS/R native SRL). A shared run-time library
(SRL) available to TNS/R native processes in both the Guardian and Open System