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-8
Expand line-handler process
Expand line-handler process. A process pair that handles incoming and outgoing Expand
messages and packets. An Expand line-handler process handles direct links and also
binds to other processes using the Network Access Method (NAM) interface to support
Expand-over-X.25, Expand-over-FOX, Expand-over-ServerNet, Expand-over-TCP/IP,
and Expand-over-SNA links. See also Expand-over-ServerNet line-handler process
(Expand/SvNet).
Expand network. The HP NonStop™ operating system network that extends the concept of
fault-tolerant operation to networks of geographically distributed NonStop systems. If
the network is properly designed, communication paths are constantly available even if
there is a single line failure or component failure.
Expand node. A system in an Expand network. See also node.
Expand node number. A number in the range 0 through 254, sometimes referred to as the
system number. The Expand node number is used to identify a node in an Expand
network. Each Expand node number must be unique within the network. See also
ServerNet node number.
Expand-over-ServerNet line. The single line associated with an Expand-over-ServerNet
line-handler process. An Expand-over-ServerNet line has the same name and logical
device number as its Expand-over-ServerNet line-handler process. However, it does
not have the same states as the line-handler process.
Expand-over-ServerNet line-handler process (Expand/SvNet). An Expand line-handler
process that uses the NETNAM protocol to access the network access method (NAM)
interface provided by the ServerNet monitor process, $ZZSCL. The
Expand-over-ServerNet line-handler process handles incoming and outgoing Expand
messages. It also handles packets leaving the server and security-related messages
going between systems within the cluster. Each node in a ServerNet cluster must be
configured with an Expand-over-ServerNet line-handler process for each other node in
the ServerNet cluster.
extensible input/output (XIO). A redesign of the HP NonStop™ operating system I/O
subsystem to enable it to extend itself in general ways to meet future requirements.
external fabric connection. The low-level ServerNet connection between a node and one
of the external ServerNet fabrics. Each node has an X and a Y connection to the
external fabrics.
external routing. The routing of packets over the external ServerNet fabrics—that is,
between systems (or nodes) in a ServerNet cluster. See also internal routing.
external ServerNet fabrics. The fabrics that link systems in a ServerNet cluster. See also
internal ServerNet fabric.
external system area network manager process (SANMAN). (1) A process that provides
management access to the external ServerNet X and Y fabrics.