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-5
cyclic redundancy check (CRC)
Class 2, and Class 3 according to the risk of causing a system outage if the
documented replacement procedure is not followed correctly and how much
CRU-replacement training or experience is advisable. See also field-replaceable unit
(FRU).
cyclic redundancy check (CRC). The most widely used error detection code for ensuring
the integrity of transmitted data. The digits of the CRC are calculated by the sender for
each block of data sent and recalculated by the receiver. It is a family of mathematical
functions involving computing the quotient and remainder of a polynomial division. A
CRC is a form of checksum. See also checksum.
dedicated LAN. An Ethernet LAN for use only by OSM applications. This LAN connects
system consoles with the Ethernet ports on the processor multifunction (PMF) CRUs in
group 01 of a NonStop S-series server. A dedicated LAN supports NonStop S-series
servers and system consoles but does not support any other types of servers or
workstations. See also public LAN.
Dense Wave Division Multiplexer (DWDM). A hardware device that converts multiple
optical signals into different wavelengths or optical channels. A DWDM can save on
fiber costs by transmitting multiple channels over a single fiber.
destination ServerNet ID (DID). A field in the ServerNet packet header indicating the
intended destination for the packet.
detailed report. A complete listing of status or configuration information provided by the
Subsystem Control Facility (SCF) STATUS or INFO command when you use the
DETAIL option. Contrast with summary report
dial-out point. A system console from which incident reports are sent to a service provider.
Incident reports are sent only from the system consoles defined as the primary and
backup dial-out points.
DID. See destination ServerNet ID (DID)
.
discovery. For the OSM package, the process of identifying the resources that exist on a
NonStop S-series server.
disk drive. A device that stores and accesses data on a disk. The two types of disk drives
are magnetic and optical. Random access to addressable locations on a magnetic disk
is provided by magnetic read/write heads. Random access to addressable locations on
an optical disk is provided by a low-intensity laser. Optical disk drives are not
supported for NonStop S-series servers. See also volume
.
DNS. See Domain Name System (DNS).
DNS server. A server that resolves hostnames to Internet protocol (IP) address mapping
queries. These queries originate either from client computers, which are known as
resolvers, or from other Domain Name System (DNS) servers, which accounts for the
distributed nature of DNS. See also Domain Name System (DNS) and node.