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-30
endian
endian. Denotes the significance of byte 0 in a multibyte structure such as a word. NonStop
servers are big-endian, where the most significant bit is contained in byte 0. Intel
systems and HP AlphaServer OpenVMS and HP AlphaServer Tru64 UNIX systems
are little-endian, where the least significant bit is contained in byte 0.
environmental parameters. Subsystem Control Facility (SCF) session parameters set by
default or by using various SCF commands. The values associated with the
environmental parameters can be examined using the ENV command.
environment strings. For an Open System Services (OSS) process, a vector of strings of
the form
name = value that contains information about the environment that the
process runs in. Environment strings are accessible to the process and are inherited by
its child processes.
Enterprise Storage System (ESS). A collection of magnetic disks, their controllers, and the
disk cache in a stand-alone cabinet or cabinets. These disks are configured by an
attached console and presented to the attached server as logical volumes that can be
a fraction of a physical volume or can span volumes.
EPO. See emergency power off (EPO).
Epoch. The period beginning January 1, 1970, at 0 hours, 0 minutes, and 0 seconds
Coordinated Universal Time (UTC)
.
EPO connector. See emergency power-off (EPO) connector.
equipment grounding conductor. The conductor used to connect the non-current-carrying
metal parts of equipment, raceways, and other enclosures to the grounding electrode
conductor at the facility’s main service entrance or at the source of a separately
derived power source.
errno. An external variable that contains the most recent error condition set by a C function.
error number. For the Subsystem Programmatic Interface (SPI), a value that can be
assigned to a return token or to the last field of an error token to identify an error that
occurred. SPI defines a small set of error numbers, but most error numbers are defined
by subsystems.
ESD kit. See electrostatic discharge (ESD) protection kit.
ESP. See expansion service processor (ESP).
ESS. See Enterprise Storage System (ESS).
essential firmware. Code in memory that is necessary for power-up initialization and
communication with a host or device. Contrast with nonessential firmware
.