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-38
FIRINIT
FIRINIT. A diagnostic task used to update the communications line interface processor
(CLIP) FRU information record (FIR) that is kept in the ServerNet wide area network
(SWAN) concentrator CLIP flash memory.
FIRMUP. A diagnostic task used to update the copy of the Portable Silicon Operating
System (pSOS) system product embedded kernel that is kept in the ServerNet wide
area network (SWAN) concentrator communications line interface processor (CLIP)
flash memory.
firmware. Code in memory that is necessary for the power-up initialization and
communication with a host or device. The software for components of the ServerNet
architecture (for example, an adapter) is called firmware. Some firmware for ServerNet
components is downloaded when the system or component is loaded.
fixed process configuration. Using Subsystem Control Facility (SCF) to configure a
generic process to always start in the first available processor (that is, to be fault
tolerant).
flag. In a UNIX or Open System Services (OSS) command, a character sequence that
begins with a hyphen and is processed as a unit.
flash memory. A type of memory that contains essential firmware and nonessential
firmware.
flash PROM. A type of programmable read-only memory (PROM) that is electrically
reprogrammable.
flat segment. A type of logical segment. Each flat segment has its own distinct address
range within the process address space that never overlaps the range of any other
allocated segments. Thus all allocated flat segments for a process are always available
for use concurrently. See also logical segment
and selectable segment.
flexible disk configuration (FDC). Configuration of an internal mirrored disk volume such
that no single processor enclosure or I/O enclosure can result in loss of online access
to the volume.
foreground process. An Open System Services (OSS) process that belongs to a
foreground process group.
foreground process group. In the Open System Services (OSS) environment, a process
group whose members have privileges for access to their controlling terminal that are
denied to processes in background process groups of that terminal. Each session with
a controlling terminal has only one foreground process group for that terminal. Contrast
with background process group
.
foreground process group ID. In the Open System Services (OSS) environment, the
process group ID of a foreground process group.