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-52
I/O controller
I/O controller. The hardware logic that controls computer I/O operations for a particular set
of devices, such as disks, tapes, terminals, or communications lines. See also
ServerNet addressable controller (SAC)
.
I/O enclosure. An HP NonStop™ S-series system enclosure containing one module, which
includes ServerNet adapters, disk drives, components related to the ServerNet fabrics,
and components related to electrical power and cooling for the enclosure. An I/O
enclosure is identical to a processor enclosure except that it contains I/O multifunction
(IOMF) customer-replaceable units (CRUs) instead of processor multifunction (PMF)
CRUs.
IOMF CRU. See I/O multifunction (IOMF) CRU.
IOMF 2 CRU. See I/O multifunction (IOMF) 2 CRU.
I/O multifunction (IOMF) CRU. (1) An HP NonStop™ S-series customer-replaceable unit
(CRU) that connects an I/O enclosure to a processor enclosure through a ServerNet
cable and supplies power to the components within the IOMF CRU as well as
redundantly to the disk drives, SCSI terminators, and ServerNet adapters in that
enclosure. The IOMF CRU contains a power supply, a service processor (SP), a
ServerNet router, an Ethernet controller, an external ServerNet port, and three SCSI
ServerNet addressable controllers (S-SACs) in a single unit. (2) A collective term for
both IOMF CRUs and IOMF 2 CRUs when a distinction between the two types of
CRUs is not required.
I/O multifunction (IOMF) 2 CRU. An HP NonStop™ S-series customer-replaceable unit
(CRU) that connects an I/O enclosure to a processor enclosure through a ServerNet
cable and supplies power to the components within the IOMF 2 CRU as well as
redundantly to the disk drives, SCSI terminators, and ServerNet adapters in that
enclosure. The IOMF 2 CRU contains a power supply, a service processor (SP), a
ServerNet router 2, an Ethernet controller, three configurable ServerNet ports, and
three SCSI ServerNet addressable controllers (S-SACs) in a single unit. IOMF 2 CRUs
are supported on G06.10 and later release version updates (RVUs).
IOP. See input/output process (IOP).
IP. See Internet protocol (IP).
IP address. An address that uniquely identifies a specific host system within a network to
the Internet protocol (IP). An IP address consists of two parts: a network address,
which identifies the network, and a local address, which identifies the host within the
network. IP routes data between source and destination IP addresses.
iPAQ Desktop. An Internet-based computing model and business PC used for Internet
access, mainstream computing, and running the Windows 2000 Professional operating
system. The iPAQ Desktop is designed to reduce hardware and software conflicts. It
eliminates Industry Standard Architecture (ISA)/Peripheral Component Interconnect
(PCI) slots and uses Universal Serial Bus (USB) ports with the Windows 2000 or
Windows ME operating system.