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-19
persistent process
persistent process. A process that must always be either waiting, ready, or executing.
These processes are usually controlled by a monitor process that checks on the status
of persistent processes and restarts them if necessary.
physical interface (PIF). The hardware components that connect a system node to a
network.
PIC. See plug-in card (PIC).
PIF. See physical interface (PIF).
ping. A utility used to verify connections to one or more remote hosts. The ping utility uses
the Internet control message protocol (ICMP) echo request and echo reply packets to
determine whether a particular IP system on a network is functional. The ping utility is
useful for diagnosing IP network or router failures.
planned outage. Time during which a system is not capable of doing useful work because
of a planned interruption. A planned outage can be time when the system or user
application is shut down to allow for servicing, upgrades, backup, or general
maintenance.
plug-in card (PIC). A replaceable component that provides a unique function when installed
in a CRU or FRU. For example, plug-in cards for the modular SEBs (MSEBs) provide a
choice of connection media for attaching ServerNet cables.
PMF CRU. See processor multifunction (PMF) CRU.
port. (1) A data channel that connects to other devices or computers. (2) A connector to
which a cable can be attached. The system transmits and receives data or requests
through ports on ServerNet adapters and processor multifunction (PMF) customer-
replaceable units (CRUs). A port is also called a connector. (3) The entrance or
physical access point (such as a connector) to a computer, multiplexer, device, or
network where signals are supplied, extracted, or observed.
position ID. A character that indicates the position a cluster switch occupies in one of the
star topologies. The position ID is a component of the two-character cluster switch
name. The cluster switch name includes an external fabric ID (X or Y) as the first
character and a position ID as the second character. For example, the cluster switch
name X3 indicates that the cluster switch serves the external ServerNet X fabric and
occupies position 3 in the topology. Position ID is not used in the layered topology.
primary path. A path enabled as the preferred path. When a primary path is disabled, an
alternate path becomes the primary path. Contrast with alternate path.
primary processor. The processor that is designated as owning the ServerNet addressable
controller (SAC) connected to separate processors running the HP NonStop™
operating system. The primary processor is the processor that has direct control over
the SAC. Contrast with backup processor.