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-48
impedance
impedance. The total opposition (that is, resistance and reactance) a circuit provides to the
flow of alternating current at a given frequency.
implementation-defined. Not specified by a standard. A correct value or behavior that is
implementation-defined can vary from system to system and therefore might represent
a feature or facility that cannot be ported.
implicit library. A library supplied by HP that is available in the read-only and execute-only
globally mapped address space shared by all processes without being specified to the
linker or loader. See also TNS system library
and public library.
implicit library import library (imp-imp). See import library.
implied user library. A method of binding TNS object files that have more than 16 code
segments. Segments 16 through 31 are located in the user code (UC) space but are
executed as if they were segments 0 through 15 of the user library (UL) code space.
This method precludes the use of a user library. Binder now supports 32 segments of
UC space concurrently with 32 segments of UL code space, so the implied user library
method is not needed in new or changed TNS applications.
import. To refer to a symbol definition from another loadfile. A loadfile imports a symbol
definition when it needs a data item or function having that symbolic name.
import control. The characteristic of a loadfile that determines from which other loadfiles it
can import symbol definitions. The programmer sets a loadfile’s import control at link
time. That import control can be localized, globalized, or semiglobalized. A loadfile’s
import control governs the way the linker and loader construct that loadfile’s searchList
and affects the search only for symbols required by that loadfile.
import library. A file that represents a dynamic-link library (DLL) and can substitute for it as
input to the linker. Import libraries facilitate linking on auxiliary platforms (that is, PCs)
where it is inconvenient to store the actual DLLs.
in-band control (IBC). A symbol-based communications protocol for communicating
management information across a ServerNet link without interfering with any
application traffic in the network. In ServerNet II architecture, IBC traffic uses standard
ServerNet packets. ServerNet I architecture uses the Illegal Symbol variation of IBC,
which uses a subset of the available symbols to convey control information from one
node to another. The symbol subset chosen is from the group of symbols that are not
used for passing data. These symbols are usually considered illegal or unused.
incident report. A report sent by the OSM or TSM server software to the respective OSM
or TSM Notification Director. If remote notification (dial-out) is configured, the
Notification Director forwards incident reports to a service provider. The three types of
incident reports are problem incident reports, periodic incident reports, and software
configuration incident reports.