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-12
HP NonStop ServerNet Switch (model 6780)
uninterruptible power supply (UPS), and AC transfer switch, and it can be packaged in
a switch enclosure or in a 19-inch rack. See also HP NonStop ServerNet Switch
(model 6780).
HP NonStop ServerNet Switch (model 6780). The cluster switch used in the layered
topology. The 6780 switch consists of a switch logic board, a midplane, plug-in cards,
power supplies, and fans. See also HP NonStop Cluster Switch (model 6770).
IBC. See in-band control (IBC).
IEEE 802.3 protocol. Institute of Electrical and Electronics Engineers (IEEE) standard
defining the hardware layer and transport layer of (a variant of) Ethernet. The
maximum segment length is 500 meters and the maximum total length is 2.5
kilometers. The maximum number of hosts is 1024. The maximum packet size is 1518
bytes.
in-band control (IBC). A symbol-based communications protocol for communicating
management information across a ServerNet link without interfering with any
application traffic in the network. In ServerNet II, IBC traffic is via standard ServerNet
packets. ServerNet I used the Illegal Symbol variation of IBC. This technique uses a
subset of the available symbols to convey control information from one node to
another. The symbol subset chosen is from the group of symbols that are not for
passing data; these symbols are usually considered illegal or unused.
incident report. A report sent by the OSM software to the OSM Notification Director If
remote notification (dial-out) is configured, the OSM Notification Director forwards
incident reports to a service provider. The three types of incident reports are problem
incident reports, periodic incident reports, and software configuration incident reports.
input/output process (IOP). A running program (part of the HP NonStop™ operating
system) that manages the I/O functions for one or more ServerNet addressable
controllers (SACs) of the same type.
internal routing. The routing of packets within a node. See also external routing.
internal ServerNet fabric. The X or Y fabric that links ServerNet devices within a node.
See also external ServerNet fabrics.
Internet protocol (IP). A data communications protocol that handles the routing of data
through a network, which typically consists of many different subnetworks. IP is
connectionless; it routes data from a source address to a destination address. See also
IP address.
interprocessor communication (IPC). The exchange of messages between processors in
the same system or node.
I/O enclosure. A NonStop S-series system enclosure containing one module, which
includes ServerNet adapters, disk drives, components related to the ServerNet fabrics,
and components related to electrical power and cooling for the enclosure. An I/O