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-105
switch logic board
switch logic board. See cluster switch logic board.
switch mode power supply. A computer power supply that uses a pulse-width modulation
switching inverter and nonlinear current draw characteristics. Switch-mode power
supplies are widely used because of their small size and efficiency.
switch rack. See cluster switch rack.
switch zone. See cluster switch zone.
switched connect. Connection to the Enterprise Storage System (ESS) through a Fibre
Channel switch (FC switch).
symbol. (1) The symbolic name of a value, typically a function entry point or a data location.
In the context of loadable libraries, symbols are defined in loadfiles and referenced in
the same or other loadfiles. (2) Within the ServerNet architecture, the nine or more bits
that encode 8-bit data and protocol commands.
symbolic link. In the Open System Services (OSS) file system and Network File System
(NFS), a type of special file that acts as a name pointer to another file. A symbolic link
contains a pathname and can be used to point to a file in another fileset. Symbolic links
are not included in ISO/IEC IS 9945-1:1990. Contrast with hard link
.
symbolic reference. An occurrence in code or data of the value of a symbol. The symbolic
reference is bound (resolved and made usable) by assigning to it the value of a
definition of that symbol. The symbol value is normally the address of a function or
variable named by the symbol. In position-independent code (PIC) loadfiles, symbolic
references occur only in data.
symbols region. See Inspect region.
SYSGENR. The system generation program that generates a customized version of the HP
NonStop™ Kernel operating system.
SYSnn subvolume. A subvolume on the $SYSTEM volume where the new version of the
HP NonStop™ Kernel operating system image is located. Also located on the SYS
nn
subvolume is system-dependent and release version update (RVU)-dependent
software.
nn is an octal number in the range %00 through %77.
SYSPOOL. The system data space that remains in memory after all system data structures
are built by the HP NonStop™ Kernel operating system at the time of a processor load.
system. All the processors, controllers, firmware, peripheral devices, software, and related
components that are directly connected together to form an entity that is managed by
one HP NonStop™ Kernel operating system image and operated as one computer.
See also node
.
system area network management process. See external system area network manager
process (SANMAN).