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-63
multifunction I/O board (MFIOB)
multifunction I/O board (MFIOB). A ServerNet adapter that contains ServerNet
addressable controllers (SACs) for SCSI and Ethernet; a service processor; ServerNet
links to the processor, to the two ServerNet adapter slots, and to one of the ServerNet
expansion board (SEB) slots; and connections to the serial maintenance bus (SMB),
which connects components within an enclosure to the service processor.
multilane link. A communication link between HP NonStop™ Cluster Switches that can
consist of multiple ServerNet cables. Two-lane links and four-lane links are examples
of multilane links.
multimode fiber-optic (MMF) plug-in card (PIC). A plug-in card (PIC) for the modular
ServerNet expansion board (MSEB) and I/O multifunction (IOMF) 2 customer-
replaceable unit (CRU) that supports the multimode fiber-optic (MMF) interface.
multimode fiber-optic (MMF) ServerNet cable. A fiber-optic cable that either allows more
than one mode to propagate or supports propagation of more than one mode of a
given wavelength. MMF ServerNet cable typically supports shorter transmission
distances than single-mode fiber-optic (SMF) ServerNet cable
.
multiplexed. The action of separating data traffic from one line onto several distinct lines or
of combining data traffic from several distinct lines onto one line.
mutex. See mutual exclusion (mutex).
mutual exclusion (mutex). An operating mode with interrupts disabled.
NAM. See Network Access Method (NAM).
named resource list (NRL). A table that contains one entry for each device and named
process in the system. A logical device number (ldev)
is an NRL index.
national-standards-body conforming POSIX.1 application. An application that both:
•
Uses only the facilities described in ISO/IEC IS 9945-1:1990 and approved
standards of a specific member of the ISO or IEC (the national standards body)
•
Documents use of only those facilities and approved standards and documents all
options and dependencies on limits
native. An adjective that can modify object code, object file, process, procedure, and mode
of process execution. Native object files contain native object code, which directly uses
the MIPS processor's instruction set and the corresponding conventions for register
handling and procedure calls. Native processes are those created by executing native
object files. Native procedures are units of native object code. Native mode execution
is the state of the process when it is executing native procedures.
native link editor. See nld utility.
native mode. See TNS/R native mode.