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-92
ServerNet cluster subsystem
ServerNet cluster subsystem. The subsystem managed by the ServerNet cluster monitor
process (SNETMON). The subsystem name is SCL. The subsystem number is 218.
The subsystem identifier is ZSCL.
ServerNet/DA. See ServerNet device adapter (ServerNet/DA).
ServerNet device. Interface logic that is associated with a specific hardware unit, such as a
processor or I/O adapter, and that provides the interface to the ServerNet
communications network. The responsibilities of the ServerNet device are to transform
message data into ServerNet packets, to transmit those packets, to receive ServerNet
packets, and to unpack the data on behalf of the associated hardware unit. See also
ServerNet subdevice
.
ServerNet device adapter (ServerNet/DA). A ServerNet adapter that controls external
devices. The 6760 ServerNet/DA contains up to four ServerNet addressable controllers
(SACs), each of which can control either disk drives or tape drives.
ServerNet device ID. See ServerNet ID.
ServerNet diagram. A graphical layout of the logical connections between objects in the
system. These objects can include processors, ServerNet routers, ServerNet adapters,
disks on the SCSI bus, and so on.
ServerNet dump. To copy the memory of a processor to disk by using the ServerNet
fabrics.
ServerNet end device. See ServerNet device.
ServerNet expansion board (SEB). (1) A connector board that plugs in to the backplane to
allow one or more ServerNet cables to exit the rear of the enclosure. The SEBs and
ServerNet cables allow processors in one group to communicate with processors in
another group. Each SEB provides either the ServerNet X fabric or the ServerNet Y
fabric for a group. (2) A collective term for both SEBs and modular SEBs (MSEBs)
when a distinction between the two types of SEBs is not required.
ServerNet extender module (SEM). Equipment that increases the distance that ServerNet
signals can be transmitted over fiber-optic cables to 40 kilometers. If multimode
fiber-optic (MMF) and single-mode fiber-optic (SMF) ServerNet cables are used in the
same system, the SEM converts MMF signals so that they can be transmitted by SMF
ServerNet cables and converts SMF signals so that they can be transmitted by MMF
ServerNet cables.
ServerNet/FX adapter. A ServerNet adapter that logically extends the ServerNet X and Y
fabrics to other clusters in a Fiber Optic Extension (FOX) ring by using fiber-optic lines.
Two 6740 ServerNet/FX adapters are used, one for the X ring and one for the Y ring.
ServerNet/FX 2 adapter. A ServerNet adapter that logically extends the ServerNet X and Y
fabrics to other clusters in a Fiber Optic Extension (FOX) ring by using fiber-optic lines.
Two 6742 ServerNet/FX 2 adapters are used, one for the X ring and one for the Y ring.