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-7
EMI
incurred during the procedure is discharged safely to the enclosure instead of to
electrical components within the enclosure.
EMI. See electromagnetic interference (EMI).
emitter-coupled logic (ECL). A logic that expresses digital signals in differential negative
voltage levels, from -8 volts to -1.8 volts. NonStop S-series servers that contain
ServerNet expansion boards (SEBs) use ECL cables. An ECL plug-in card (PIC)
allows the modular SEB (MSEB) to use ECL ServerNet cables.
EMS. See Event Management Service (EMS).
EMS collector. An Event Management Service (EMS) process to which subsystems report
events.
enclosure. Similar to a cabinet in NonStop K-series systems. In a NonStop S-series server,
an enclosure can contain components of a system or a peripheral. Base enclosures
are placed on the floor and can have other enclosures stacked on top of them.
Stackable enclosures can be placed on top of other enclosures. See also system
enclosure.
error number. For the Subsystem Programmatic Interface (SPI), a value that can be
assigned to a return token, or to the last field of an error token, to identify an error that
occurred. SPI defines a small set of error numbers, but most error numbers are defined
by subsystems.
ESD kit. See electrostatic discharge (ESD) protection kit.
Ethernet. A local area network (LAN) that uses the carrier sense multiple access with
collision detection (CSMA/CD) access method on a bus topology and is the basis for
the IEEE 802.3 standard.
Ethernet 4 ServerNet adapter (E4SA). A ServerNet adapter for Ethernet local area
networks (LANs) that contains four Ethernet ports.
Ethernet hub. A multiport repeater typically supporting 10BaseT cabling. Most hubs are
connectors for 8 or 12 cables. Also referred to as a concentrator.
Event Management Service (EMS). A Distributed Systems Management (DSM) product
that provides event collection, event logging, and event distribution facilities. EMS
provides different event descriptions for interactive and programmatic interfaces, lets
an operator or an application select specific event-message data, and allows for
flexible distribution of event messages within a system or network.
event message. Text intended for a system operator that describes a change in some
condition in the system or network, whether minor or serious. The change of condition
is called an event. Events can be operational errors, notifications of limits exceeded,
requests for actions needed, and so on. See also operator message.