Bond Failover

Either of the following failure scenarios can induce bond failover:

• An active interface detects a link state failure in another monitored interface
• ClusterXL detects a failure in sending or receiving Cluster Control Protocol (CCP) keep-alive packets

Either of these occurrences will induce a failover, either to another slave interface within the bond, or between cluster members, depending on the circumstances.

Note - The bond failover operation requires a network interface card that supports the Media-Independent Interface (MII) standard.

Included Topics Link State Initiated Failover CCP Initiated Failover

Link State Initiated Failover

Link-state initiated failover occurs in this sequence:

1. The active slave interface detects a down link state.
2. The bond initiates failover to a standby interface. Since this is a failover within the bond, the status of the other cluster member is unaffected.

   When the number of available slave interfaces is fewer than the critical minimum number of interfaces, failover to other cluster members occurs.

3. If the standby interface continues to detect a link failure, and the initial interface is still down, failover to other cluster members occurs.

CCP Initiated Failover

CCP failover occurs only when other cluster members are not down, in this sequence.

1. ClusterXL detects a problem sending or receiving of CCP packets.
2. ClusterXL initiates an internal bond failover.
3. ClusterXL monitors CCP packet transmission and reception. If additional problems are detected within three minutes, the system initiates a failover to another cluster member.