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-91
ServerNet II
ServerNet II. The second-generation ServerNet network. ServerNet II architecture is
backward-compatible with ServerNet I architecture, and it features 125 (or 50)
megabytes/second speed, 12-port ServerNet routers, 8b/9b and 8b/10b (serializer
ready) encoding, and a 512-byte maximum packet size. See also ServerNet I
.
ServerNet adapter. A component that connects peripheral devices to the rest of the system
through a ServerNet bus interface (SBI). A ServerNet adapter is similar in function to
an I/O controller logic board (LB) and backplane interconnect card (BIC) in HP
NonStop™ K-series servers.
ServerNet address. A virtual memory address that, when translated to a physical address,
indicates where the memory access needed by a ServerNet transaction begins. In
some cases, the translation can point to some entity other than memory, such as a
register. The ServerNet address is included in all ServerNet read request and write
request packets.
ServerNet addressable controller (SAC). An I/O controller that is uniquely addressable by
a ServerNet ID in the ServerNet fabrics. A SAC is typically implemented on some
portion of a processor multifunction (PMF) customer-replaceable unit (CRU), an I/O
multifunction (IOMF) CRU, or a ServerNet adapter.
ServerNet buffer board (SBB). The board that provides the ServerNet connection to and
from the I/O multifunction (IOMF) customer-replaceable unit (CRU). This board
replaces the processor and memory board (PMB) in the IOMF CRU.
ServerNet bus interface (SBI). The I/O control and expansion packetizer application-
specific integrated circuit (ASIC).
ServerNet cable. A cable that provides ServerNet links between system enclosures.
ServerNet cluster. A network of servers (nodes) connected together using the ServerNet
protocol for interprocessor communication across a cluster and within its nodes. A
ServerNet cluster offers linear system expansion beyond the 8-processor or
16-processor limits of a single server, achieving comparable speeds for internal and
external ServerNet communication. See also cluster
and HP NonStop™ ServerNet
Cluster (ServerNet Cluster).
ServerNet Cluster. See HP NonStop™ ServerNet Cluster (ServerNet Cluster).
ServerNet cluster monitor process (SNETMON). A process pair with the process name
$ZZSCL that manages the state of the ServerNet cluster subsystem. Each node
(system) in a ServerNet cluster must have one SNETMON process pair running.
ServerNet cluster services. The functions necessary to allow a node to join, participate in,
or leave an HP NonStop™ ServerNet Cluster. These functions include monitoring and
control of the physical connections to the cluster, discovery of other nodes in the
cluster, and automatic recovery of failed connections.