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-99
SNDA
Inspect and Inspect can be used to debug snapshots, but the Inspect product refers to
a snapshot a save file
.
SNDA. See ServerNet device adapter (ServerNet/DA).
SNETMON. See ServerNet cluster monitor process (SNETMON).
SNMP. See Simple Network Management Protocol (SNMP).
SNMP task. A task that runs in each ServerNet wide area network (SWAN) concentrator
communications line interface processor (CLIP) as part of the WAN architecture. This
task accepts and replies to Simple Network Management Protocol (SNMP) request
messages.
socket. An end-point for stream-oriented communication. A socket has a file descriptor.
soft reset. An action performed on an HP NonStop™ Cluster Switch that restarts the
firmware on the cluster switch but does not interfere with ServerNet passthrough data
traffic.
software configuration incident report. A type of incident report that reports changes in
the software configuration of the server. A software configuration incident report
includes the server’s software configuration file.
software product revision (SPR). The method of releasing incremental software updates
on HP NonStop™ S-series systems. An SPR can include one or more corrections to
code, or it can contain code that adds new function to a software product.
source ServerNet ID (SID). A field in the ServerNet packet header indicating the source of
the packet.
SP. See service processor (SP).
special character. A character entered from a terminal that has an effect other than being
part of the input stream from that terminal.
special file. A file in the Open System Services (OSS) file system that is not a regular file.
Special files include directories, FIFOs, and character special files such as terminal
device files. Contrast with regular file
.
SP event message. See service processor (SP).
SPI. See Subsystem Programmatic Interface (SPI).
S-PIC. See SCSI plug-in card (S-PIC).
split-star topology. A network topology that uses up to two HP NonStop™ Cluster
Switches for each external fabric. External routing is implemented between the two
starred halves of a ServerNet cluster. (A starred half consists of up to eight nodes
attached to one set of cluster switches.) The starred segments are joined by four-lane