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-35
field
field. In a structured programming language, an addressable entry within a data structure.
The term
field is sometimes used to mean member.
field-programmable gate array (FPGA). A programmable integrated circuit that can be
customized to perform specific functions.
field-replaceable unit (FRU). A unit that can be replaced in the field only by qualified
personnel trained by HP and cannot be replaced by customers. A unit is classified as a
FRU because of safety hazards such as weight, size, sharp edges, or electrical
potential; contractual agreements with suppliers; or national or international standards.
See also customer-replaceable unit (CRU)
.
FIFO. A type of Open System Services (OSS) special file that is always read and written in
a first-in, first-out manner.
FIFO special file. See FIFO.
file. An object to which data can be written or from which data can be read. A file has
attributes such as access permissions and a file type. In the Open System Services
(OSS) environment, file types include regular file, character special file, block special
file, FIFO, and directory. In the Guardian environment, file types include disk files,
processes, and subdevices.
file class. The property of an Open System Services (OSS) file indicating access
permissions for a process related to the owner, group, or other identification of the
process. See also file group class
, file other class, and file owner class.
file description. See open file description.
file descriptor. In the Open System Services (OSS) file system, the nonnegative integer
that uniquely identifies a single open of a file to a running process. Each file descriptor
is associated with an open file description that contains data about the file.
file group class. The property of an Open System Services (OSS) file indicating access
permissions for a process related to the group ID of the process. A process is in the file
group class of a file if both:
•
The process is not a member of the file owner class for the file.
•
The process has an effective group ID or supplementary group ID that is the same
as the group ID associated with the file.
file identifier. In the Guardian environment, the portion of a filename following the
subvolume name. In the Open System Services (OSS) environment, a file identifier is a
portion of the internal information used to identify a file in the OSS file system (an
inode number). The two identifiers are not comparable.
file link count. The total number of directory entries for an Open System Services (OSS)
file within an HP NonStop™ node.