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-9
external system area network manager process
(SANMAN)
external system area network manager process (SANMAN). (1) A Guardian process
with the name $ZZSMN that provides management access to the external ServerNet X
and Y fabrics. (2) A Windows NT process that configures and maintains ServerNet
switches within a Windows NT cluster.
fabric. A complex set of interconnections through which there can be multiple and (to the
user) unknown paths from point to point. The term fabric is used to refer to the X or Y
portion of the ServerNet communications network; for example, the X fabric.
factory-installed operating system. The version of the operating system image that HP
creates with a CONFTEXT file, OSIMAGE file, and configuration database that
matches your order. Your system is shipped with this version installed in the system
subvolume $SYSTEM.SYS00.
Fast Ethernet ServerNet adapter (FESA). A single-ported ServerNet adapter that supports
100-megabit per second (Mbps) and 10-Mbps Ethernet data transfer rates on a
NonStop S-series server. The FESA installs directly into an existing Ethernet port, and
one FESA is supported per system enclosure.
fault tolerance. The ability of a NonStop system to continue processing despite the failure
of any single software or hardware component within the system.
FESA. See Fast Ethernet ServerNet adapter (FESA).
Fiber Optic Extension (FOX). Refers to two products, FOX II and ServerNet/FX, which
allow you to create high-speed (up to 4 megabytes/second) networks of as many as 14
systems connected by dual fiber-optic cables.
fiber-optic ServerNet cable. A ServerNet cable using a medium for data transmission that
conveys light or images through glass or plastic fibers. Fiber-optic cables (light guides)
are a direct replacement for conventional coaxial cable and wire pairs. NonStop
S-series servers support two types of fiber-optic ServerNet cables: single-mode and
multimode. See also multimode fiber-optic (MMF) cable
and single-mode fiber-optic
(SMF) cable.
field-programmable gate array (FPGA). A programmable integrated circuit that can be
customized to perform specific functions.
field-replaceable unit (FRU). A unit that can be replaced in the field only by qualified
personnel trained by HP and cannot be replaced by customers. A unit is classified as a
FRU because of safety hazards such as weight, size, sharp edges, or electrical
potential; contractual agreements with suppliers; or national or international standards.
See also customer-replaceable unit (CRU).
file name. A unique name for a file. File names for disk files normally have at least two parts
(the disk name and the file name); an example of a file name on a PC is B:MYFILE. In
the Guardian environment on a NonStop S-series system, disk file names include a
disk volume name, a subvolume name, and a file identifier. An example of such a file