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-8
block
block. A grouping of one or more system enclosures that an HP NonStop™ S-series
system recognizes and supports as one unit. A block can consist of either one
processor enclosure, one I/O enclosure, or one processor enclosure with one or more
I/O enclosures attached.
blocked signal. A programmatic signal that is currently in the pending signal mask of a
process and, when generated, is not delivered to the process because of the signal
mask setting. Some signals cannot be blocked.
block special file. In the Open System Services (OSS) environment, a device that is
treated as a file for which all input or output must occur in blocks of data. Traditionally,
such files are disk or tape devices. Block special files provide access to a device in a
manner that hides the hardware characteristics of the device. Contrast with character
special file.
bond. A reliable connection that ensures the required electrical conductivity between
conductive parts that must be electrically connected.
bonded. The mechanical interconnection of conductive parts to maintain a common
electrical potential.
bonding. The permanent joining of conductive parts to form a path that ensures electrical
continuity and the capacity to safely conduct any current likely to be imposed.
bonding jumper. See main bonding jumper.
boot. A synonym for load. Load is the preferred term used in this and other HP NonStop™
S-series system publications.
BOOTP. A protocol for providing initialization information to diskless nodes in an open
network.
BOOTPC. See BOOTP client (BOOTPC).
BOOTP client (BOOTPC). A client provided as a Portable Silicon Operating System
(pSOS) system product task in the essential firmware on each communications line
interface processor (CLIP) in the ServerNet wide area network (SWAN) concentrator.
BOOTPC tasks are also provided on the host system as the WANBoot process in the
WAN subsystem.
BOOTPD. See BOOTP daemon (BOOTPD).
BOOTP daemon (BOOTPD). The BOOTP server. One BOOTPD runs as a Portable Silicon
Operating System (pSOS) system product task in the essential firmware on each
communications line interface processor (CLIP) in the ServerNet wide area network
(SWAN) concentrator. BOOTPD tasks are also provided on the host system as the
WANBoot process in the WAN subsystem.