Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Configuring OPS Clusters with MC/LockManager: > Chapter 2 Understanding MC/LockManager Hardware Configurations

Redundant Network Components

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

To eliminate single points of failure for networking, each subnet accessed by a cluster node is required to have redundant network interfaces. Redundant cables are also needed to protect against cable failures. Each interface card is connected to a different cable, and the cables themselves are joined by a connector such as a hub or a bridge. In the case of FDDI networks, each interface card is connected via a cable to a different concentrator. This arrangement of physical cables connected to each other via a bridge or concentrator or switch is known as a bridged net.

IP addresses can be associated with interfaces on a bridged net. An interface that has an IP address associated with it is known as a primary interface, and an interface that does not have an IP address associated with it is known as a standby interface. Standby interfaces are those which are available for switching by MC/LockManager if a failure occurs on the primary. When MC/LockManager detects a primary interface failure, it will switch the IP addresses and any associated connections from the failed interface card to a healthy standby interface card.

A selection of network configurations is described further inthe following sections. For a complete list of supported networks, refer to the MC/LockManager Release Notes for your version of the product.

Redundant Ethernet Configuration

The use of redundant network components is shown in Figure 2-1 “Redundant LANs ”, which is an Ethernet configuration.

Figure 2-1 Redundant LANs

Redundant LANs

In the figure, a two-node MC/LockManager cluster has one bridged net configured with both a primary and a standby LAN card for the data/heartbeat subnet (Subnet A). Another LAN card provides an optional dedicated heartbeat LAN. Note that the primary and standby LAN segments are connected by a hub to provide a redundant data/heartbeat subnet. Each node has its own IP address for this subnet. In case of a failure of a primary LAN card for the data/heartbeat subnet, MC/LockManager will perform a local switch to the standby LAN card on the same node.

Redundant heartbeat is provided by the primary LAN and the dedicated LAN which are both carrying the heartbeat. In Figure 2-1 “Redundant LANs ”, local switching is not needed for the dedicated heartbeat LAN, since there is already a redundant path via the other subnet. In case of data congestion on the primary LAN, the dedicated heartbeat LAN will prevent a false diagnosis of heartbeat failure. Each node has its own IP address for dedicated heartbeat LAN.

NOTE: You should verify that network traffic is not too high on the heartbeat/ data LAN. If traffic is too high, this LAN might not perform adequately in transmitting heartbeats if the dedicated heartbeat LAN fails.

Providing Redundant FDDI Connections

FDDI is a high speed fiber optic interconnect medium. If you are using FDDI, you can create a redundant configuration by using a star topology to connect all the nodes to two concentrators, which are also connected to two routers, which communicate with the world outside the cluster. In this case, you use two FDDI cards in each node. The configuration is shown in Figure 2-2 “Redundant FDDI Configuration”. Note that the concentrators are connected together using dual cables cross-connected Port A to Port B. The routers must be configured to send all packets to both concentrators.

Figure 2-2 Redundant FDDI Configuration

Redundant FDDI Configuration

Using Dual Attach FDDI Stations

Another way of obtaining redundant FDDI connections is to configure dual attach stations on each node to create an FDDI ring, shown in Figure 2-3 “Configuration with Dual Attach FDDI Stations ”. An advantage of this configuration is that only one slot is used in the system card cage. In Figure 2-3 “Configuration with Dual Attach FDDI Stations ”, note that nodes 3 and 4 also use Ethernet to provide connectivity outside the cluster.

Figure 2-3 Configuration with Dual Attach FDDI Stations

Configuration with Dual Attach FDDI Stations

The use of dual attach cards gives protection against failures in both cables and connectors, but does not protect against card failures. LAN card failure would result in a package switching to another node.

Fibre Channel Switched Configurations

Another type of high speed fiber optic interconnect is provided with Fibre Channel, which is normally used with larger clusters (4 to 8 nodes). MC/LockManager clusters configured on enterprise parallel server (EPS) systems can use Fibre Channel switches to provide redundant network paths among nodes. A four node example with two switches is shown in Figure 2-4 “FibreChannel Interconnect in a Four-Node Cluster ”. For a two-switch topology, all primary paths must go into one switch while all standbys must go to the second switch.

Figure 2-4 FibreChannel Interconnect in a Four-Node Cluster

FibreChannel Interconnect in a Four-Node Cluster

In the figure, the solid lines refer to the primary network path among the nodes and the dotted lines refer to the standby path. If there is a failure in one of the primary lines, a local switch takes place on the node that has a failed primary line, and the standby is used instead.

Using a Serial (RS232) Heartbeat Line

MC/LockManager supports a two-node configuration using serial (RS232) communication for heartbeats only. You select this as an alternate heartbeat interface to provide redundant heartbeat. If you configure serial (RS232) as a heartbeat line, MC/LockManager will send the heartbeat continuously on both the LAN configured for heartbeat and a monitored serial (RS232) line.

Even if you have a serial (RS232) line configured for redundant heartbeat, one LAN is still required to carry a heartbeat signal. The serial line heartbeat protects against network saturation but not against network failure, since MC/LockManager requires TCP/IP to communicate between cluster members. If both network cards fail on one node, then having a serial line heartbeat keeps the cluster up long enough to detect the LAN controller card status and to fail the node with bad network connections while the healthy node stays up and runs all the packages.

NOTE: The use of a serial (RS232) heartbeat line is supported only in a two-node cluster configuration.

A serial (RS232) heartbeat line is shown in Figure 2-5 “Two-LAN Configuration with Redundant Serial (RS232) Line ”.

Figure 2-5 Two-LAN Configuration with Redundant Serial (RS232) Line

Two-LAN Configuration with Redundant Serial (RS232) Line
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1998 Hewlett-Packard Development Company, L.P.