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-23
destination ServerNet ID (DID)
destination ServerNet ID (DID). A field in the ServerNet packet header indicating the
intended destination for the packet.
detailed report. A complete listing of status or configuration information provided by the
Subsystem Control Facility (SCF) STATUS or INFO command when you use the
DETAIL option. Contrast with summary report
.
device. A computer peripheral or an object that appears to an application as such. See also
terminal
.
DHCP. See Dynamic Host Configuration Protocol (DHCP).
dial-out point. A system console from which incident reports are sent to a service provider.
Incident reports are sent only from system consoles defined as the primary and backup
dial-out points (the primary and backup system consoles).
DID. See destination ServerNet ID (DID).
DIMM. See dual inline memory module (DIMM).
direct connect. Connection from the Fibre Channel ServerNet adapter (FCSA) to the
Enterprise Storage System (ESS)
without going through an FC switch.
direct current (DC). Electric current that flows in only one direction. Contrast with
alternating current (AC)
.
direct jump area. One of sixteen 256-megabyte portions of the 4-gigabyte virtual address
space. A RISC jump instruction has the ability to jump directly to any location within its
own direct jump area without having to use a far jump table.
directory. A type of Open System Services (OSS) special file that contains directory entries,
which associate names with files. No two directory entries in the same directory have
the same name.
directory entry. In the Open System Services (OSS) file system, an object that associates
a filename with a file. Several directory entries can associate names with the same file.
See also link
.
directory loop. In the Open System Services (OSS) file system, an error condition in which
a directory is identified as its own parent directory.
directory special file. See directory.
directory stream. In the Open System Services (OSS) file system, an object with an
opaque data type. A process can sequentially read directory entries from a directory
stream.