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-25
ServerNet switch
ServerNet switch. A point-to-point networking device that connects ServerNet nodes to a
single fabric (X or Y) of the ServerNet communications network. The ServerNet switch
routes ServerNet packets between these nodes.
service processor (SP). A physical component of the processor multifunction (PMF) CRU
or I/O multifunction (IOMF) CRU that controls environmental and maintenance
functions (including system load functions) in the enclosure. SPs operate in pairs to
provide fault tolerance. The two SPs in group 01 are designated the master service
processors (MSPs). Other pairs of SPs within a system are called expansion service
processors (ESPs).
service provider. (1) A person trained and qualified to service field-replaceable units
(FRUs). (2) An organization, such as the Global Customer Support Center (GCSC),
that helps you resolve problems with your NonStop S-series server. The OSM package
allows you to use the help of a service provider by configuring the OSM package to
support remote notification and remote access.
service side. The side of a system enclosure in a NonStop S-series server that contains,
behind an optional door, processor multifunction (PMF) customer-replaceable units
(CRUs) or I/O multifunction (IOMF) CRUs, ServerNet expansion boards (SEBs),
modular SEBs (MSEBs), and ServerNet adapters; it is opposite the appearance side.
Cables are accessed from the service side. System enclosures are typically arranged
so that the service side is the least visible side. See also appearance side.
SID. See software product revision (SPR).
single-mode fiber-optic (SMF) cable. A fiber-optic cable that allows only one mode to
propagate. SMF cable has a small-diameter core for optimized long-distance
transmission. See also multimode fiber-optic (MMF) cable.
single-wide plug-in card (PIC). A small-form-factor plug-in card (PIC) that occupies one
PIC slot within a customer-replaceable unit (CRU). See also double-wide plug-in card
(PIC).
SIT. See system image tape (SIT)
.
site update tape (SUT). One or more tapes that contain each target system’s site-specific
subvolume and various products. Each product contains a softdoc and a complete set
of files. A SUT is delivered with every new system and can be ordered whenever a
new RVU of the system software is available. A full SUT contains the current RVU of
the operating system and all product software that has been ordered with it. A partial
SUT contains a subset of products for the current software RVU.
slot. A physical, labeled space for a customer-replaceable unit (CRU)
or field-replaceable
unit (FRU) that is part of a module. A module contains one or more slots.
slot location. A 3-number identifier for a particular slot on a system that consists of the
group number, module number, and slot number; for example, 02,01,08 (group 02,
module 01, slot 08).