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-51
Internet control message protocol (ICMP)
physical network, an Internet address consists of a network portion and a host portion.
See also IP address
.
Internet control message protocol (ICMP). A maintenance protocol in the Transmission
Control Protocol/Internet Protocol (TCP/IP) suite that is required in every TCP/IP
implementation. The ICMP allows two nodes on an IP network to share IP status and
error information. The ICMP is used by the ping utility to determine the readability of a
remote system. See also IP address
and ping.
Internet protocol (IP). A data communications protocol that handles the routing of data
through a network, which typically consists of many different subnetworks. IP is
connectionless. It routes data from a source address to a destination address. See
also IP address
.
interoperability. (1) Within an HP NonStop™ node, the ability to use the features or
facilities of one environment from another. For example, the
gtacl command in the
Open System Services (OSS) environment allows an interactive user to start and use a
Guardian tool in the Guardian environment. (2) Among systems from multiple vendors
or with multiple versions of operating systems from the same vendor, the ability to
exchange status, files, and other information. Product externals and end-user
publications for the NonStop range of servers often use the term
connectivity in this
context. See also connectivity
.
interprocessor communications (IPC). The exchange of messages between processors.
intrinsic library. See Shared Millicode Library.
instance. A particular case of a class of items or objects. For example, a process is defined
as one instance of the execution of a program. Multiple processes might be executing
the same program simultaneously. Also, instance data refers to global data of a
program or library. Each process has its own instance of the data.
instance data. For each process using a dynamic-link library, a data segment area
containing the global variables used by the library.
I/O adapter module (IOAM). A collection of modular components that provides I/O
connectivity and can include ServerNet switch boards, Fibre Channel ServerNet
adapters (FCSAs), fans, and power supplies. In the IOAM, each module is a logical
entity that represents a single service domain.
I/O adapter module enclosure (IOAM enclosure). The sheet-metal carrier that is installed
in a standard 19-inch rack and contains the IOAM components.
IOAM. See I/O adapter module (IOAM).
IOAM enclosure. See I/O adapter module enclosure (IOAM enclosure).
I/O cabinet. See I/O enclosure.