ServerNet Cluster 6780 Planning and Installation Guide (G06.28+, H06.05+)
Table Of Contents
- What’s New in This Guide
- About This Guide
- 1 ServerNet Cluster Overview
- 2 ServerNet Cluster Hardware Description
- 3 Planning for Installation and Migration
- Planning Checklist
- Software Installation Planning
- Hardware Installation and Migration Planning
- Task 1: Plan for the ServerNet Nodes
- Task 2: Plan for the System Consoles
- Task 3: Plan for the 6780 Switches
- Task 4: Plan for the Racks
- Task 5: Plan for the Power Requirements
- Task 6: Plan the Location of the Hardware
- Task 7: Plan for the Fiber-Optic Cables
- Task 8: Plan to Migrate the ServerNet Nodes From 6770 Switches
- Task 9: Plan the ServerNet Node Numbers
- Task 10: Plan the Expand-Over-ServerNet Lines
- Migration Examples
- 4 Preparing a System for Installation or Migration
- 5 Installing 6780 Switches
- 6 Connecting the Fiber-Optic Cables
- Summary of Tasks
- Handling the Fiber-Optic Cables
- Connecting the Layer Cables
- Connecting the Zone Cables
- Connecting the Cables Between a Node and a 6780 Switch
- Alerts
- Task 1: Double-Check the Required Software and Hardware
- Task 2: Label the Cables That Connect to the Node
- Task 3: Inspect the Cables
- Task 4: Connect a Cable to the Switch
- Task 5: Connect a Cable to the Node
- Task 6: Check the Link-Alive LEDs
- Task 7: Check Operations
- Task 8: Finish Connecting the Fiber-Optic Cables
- Routing the Fiber-Optic Cables
- 7 Configuring Expand-Over-ServerNet Lines
- Using Automatic Line-Handler Generation
- Using the OSM Service Connection
- Using SCF
- Rule 1: Configure the Primary and Backup Line-Handler Processes in Different Processor Enclosures
- Rule 2: For Nodes With 6 or More Processors, Avoid Configuring the Line-Handler Processes in Proc...
- Rule 3: For Nodes With More Than 10 Processors, Avoid Configuring the Line-Handler Processes in P...
- Expand-Over-ServerNet Line-Handler Process Example
- 8 Checking Operations
- Checking the Operation of the ServerNet Cluster
- Checking the Operation of Each Switch
- Checking the Power to Each Switch
- Checking the Switch Components
- Checking the Numeric Selector Setting
- Checking the Globally Unique ID (GUID)
- Checking for a Mixed Globally Unique ID (GUID)
- Checking the Fiber-Optic Cable Connections to the Switch Port
- Checking the Switch Configuration, Firmware, and FPGA Images
- Checking the Operation of Each Node
- Checking the Service Processor (SP) Firmware
- Checking That Automatic Line-Handler Generation Is Enabled
- Checking the ServerNet Node Numbers
- Checking MSGMON, SANMAN, and SNETMON
- Checking for Alarms on Each Node
- Checking the ServerNet Cluster Subsystem
- Checking That the ServerNet Node Numbers Are Consistent
- Checking Communications Between a Local Node and a Switch
- Checking Communications With a Remote Node
- Checking the Internal ServerNet X and Y Fabrics
- Checking the Operation of Expand Processes and Lines
- 9 Changing a ServerNet Cluster
- OSM Actions
- Removing a Node From a ServerNet Cluster
- Removing Switches From a ServerNet Cluster
- Adding a Node to a ServerNet Cluster
- Adding a Switch Layer to a ServerNet Cluster
- Adding a Switch Zone to a ServerNet Cluster
- Task 1: Prepare to Add the Switches
- Task 2: Connect the Cables Between Layers
- Task 3: Check Operations
- Task 4: Disconnect the Cables Between Zones
- Task 5: Connect the Cables Between Zones
- Task 6: Check Operations
- Task 7: Connect the Additional Nodes
- Task 8: Check Operations
- Task 9: Repeat Tasks 2 Through 8 for the Other Fabric
- Task 10: Reenable OSM Alarms
- Moving a Node
- Changing the Hardware in a Node Connected to a ServerNet Cluster
- 10 Troubleshooting
- Symptoms
- Recovery Operations
- Enabling Automatic Expand-Over-ServerNet Line-Handler Generation
- Reseating a Fiber-Optic Cable
- Correcting a Mixed Globally Unique ID (GUID)
- Restoring Connectivity to a Node
- Switching the SANMAN Primary and Backup Processes
- Switching the SNETMON Primary and Backup Processes
- Configuring the Expand-Over-ServerNet Line-Handler Processes and Lines
- Starting Required Processes and Subsystems
- Fallback Procedures
- 11 Starting and Stopping ServerNet Cluster Processes and Subsystems
- A Part Numbers
- B Blank Planning Forms
- C ESD Guidelines
- D Specifications
- E Configuring MSGMON, SANMAN, and SNETMON
- F Updating the 6780 Switch Logic Board Firmware, Configuration, and FPGA Images
- G Using the Long-Distance Option
- Safety and Compliance
- Glossary
- Index
Glossary
ServerNet Cluster 6780 Planning and Installation Guide—527301-005
Glossary-24
ServerNet node
ServerNet node. A system (node) in a ServerNet cluster. See also node and ServerNet
cluster.
ServerNet node number. A number that identifies a member system in a ServerNet cluster.
Each node in a ServerNet cluster has a unique ServerNet node number. The
ServerNet node number is a simplified expression of the ServerNet node routing ID
that determines the node to which a ServerNet packet is routed. The ServerNet node
number is assigned based on the port to which the node is connected on the cluster
switch. You can use SCF or the OSM Service Connection to view the ServerNet node
number.
ServerNet node routing ID. A bit field used to route ServerNet packets across the external
ServerNet X and Y fabrics. The ServerNet node routing ID occupies the upper six bits
of the 20-bit ServerNet ID, and it is unique for each member, or node, in a ServerNet
cluster. This term is the fully qualified form of node routing ID.
SERVERNET object type. In the Kernel subsystem, the object type for either the $ZSNET
ServerNet subsystem manager process or the ServerNet X fabric or Y fabric.
ServerNet packet. A unit of information consisting of a header, an address field, a
0-to-64-byte data field, and a 32-bit cyclic redundancy check (CRC) checksum.
ServerNet packets negotiate the network using a technique called wormhole routing.
ServerNet port. A connector used for ServerNet links. Six ServerNet ports are located on a
ServerNet expansion board (SEB). Ten ServerNet ports are located on a modular
ServerNet expansion board (MSEB).
ServerNet router. An application-specific integrated circuit (ASIC) responsible for routing
ServerNet packets along ServerNet links in the ServerNet fabrics, using routing
information that is present within the packets. A ServerNet router acts as a fully duplex
crossbar switch, able to switch any of its input ports to any of its output ports. See
ServerNet router 1 and ServerNet router 2.
ServerNet router 1. A model of ServerNet router that, in a NonStop S-series server, has a
total of six input and six output ServerNet ports. A ServerNet router 1 is never an end
device. See also ServerNet router 2.
ServerNet router 2. A model of ServerNet router that, in a NonStop S-series server, has a
total of twelve input and twelve output ServerNet ports. A ServerNet router 2 is never
an end device. See also ServerNet router 1.
ServerNet subdevice. An I/O device that sends and receives its information through a
controlling device that acts as the ServerNet device for routing purposes.
ServerNet subdevice ID. The low-order bits (for example, the two least significant bits) of a
ServerNet ID, used by a ServerNet device to distribute incoming and outgoing
information between itself and its associated subdevices.