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-36
file mode
file mode. For an Open System Services (OSS) process, a field in the stat structure for a
specific file that describes the type and characteristics of the file and contains the
access permission bits for the file.
file mode creation mask. A mask associated with an Open System Services (OSS)
process and used when the process creates a file. Bits set in this mask are cleared in
the access permission bits for the file.
filename. In the Open System Services (OSS) environment, a component of a pathname
containing any valid characters other than slash (
/) or null. See also file name.
file name. A string of characters that uniquely identifies a file.
In the PC environment, file names for disk files normally have at least two parts (the
disk name and the file name); for example, B:MYFILE.
In the Guardian environment, disk file names include a node name, volume name,
subvolume name, and file identifier; for example, \NODE.$DISK.SUBVOL.MYFILE.
In the Open System Services (OSS) environment, a file is identified by a pathname
; for
example,
/usr/john/workfile. See also filename.
file other class. The property of an Open System Services (OSS) file indicating access
permissions for a process related to the user ID and group ID of the process. A
process is in the file other class of a file if both:
•
The process is not a member of the file owner class for the file.
•
The process is not a member of the file group class for the file.
file owner class. The property of an Open System Services (OSS) file indicating access
permissions for a process related to the user ID of the process. A process is in the file
owner class of a file if the process has an effective user ID that is the same as the user
ID (owner) associated with the file.
file permission bits. Information about an Open System Services (OSS) file that is used,
along with other information, to determine whether a process or user has read, write, or
execute/search permission to that file. The bits are divided into three parts: owner,
group, and other. Each part is used with the corresponding file class of processes.
file serial number. A number that uniquely identifies a file within its file system.
fileset. In the Open System Services (OSS) environment, a set of files with a common
mount point within the file hierarchy. A fileset can be part or all of a single virtual file
system.
On an HP NonStop™ system, the Guardian file system for a node has a mount point
and is a subset of the OSS virtual file system. The entire Guardian file system
therefore could be viewed as a single fileset. However, each volume and each process
of subtype 30 within the Guardian file system is actually a separate fileset.
The term
file system is often used interchangeably with fileset in UNIX publications.