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-83
reference page
recorded by the linker as a DLL is built. It affects only localized clients of the DLL. This
feature allows a symbol to be moved from one DLL to another without relinking clients
of the original DLL.
Reexporting is transitive; that is, if A reexports B and B reexports C, then A reexports
C. Reexported libraries can reexport other libraries to form a succession of reexported
libraries of arbitrary length.
reference page. In Open System Services (OSS) and Distributed Computing Environment
(DCE), the online or hard-copy version of a file that provides reference information for
a software facility. Some UNIX product externals and end-user publications use the
term
man page instead, referring either to the online delivery mechanism used to
display the file (usually the shell
man command) or to the nature of the file as part of a
publication.
register-exact point. A synchronization location within an accelerated object file at which
both of these statements are true:
•
All live TNS registers plus all values in memory are the same as they would be if
the object file were running in TNS mode or TNS interpreted mode or on a TNS
system.
•
All accelerator code optimizations are ended.
Register-exact points are a small subset of all memory-exact points. Procedure entry
and exit locations and call-return sites are usually register-exact points. All places
where the program might switch into or from TNS mode or TNS interpreted mode are
register-exact points. Contrast with memory-exact point
and nonexact point.
regular file. In the Open System Services (OSS) file system, a file that is a randomly
accessible sequence of bytes. A regular file contains binary or text data and has no
structure imposed by the system. Contrast with special file
.
relative pathname. In the Open System Services (OSS) file system and Network File
System (NFS), a pathname that does not begin with a slash (
/) character. A relative
pathname is resolved beginning with the current working directory. Contrast with
absolute pathname
.
release version update (RVU). A collection of compatible revisions of HP NonStop Kernel
operating system software products, identified by an RVU ID, and shipped and
supported as a unit. An RVU consists of the object modules, supporting files, and
documentation for the product revisions. An RVU also includes a set of documentation
for the overall RVU.
RELOAD. An HP Tandem Advanced Command Language (TACL) command to load the HP
NonStop™ Kernel operating system image from disk over the ServerNet fabrics into
the memory of the processor.
remote access. A form of remote support, configured in OSM and TSM Notification
Director. Remote access, or dial-in, allows a service provider to dial in to your system