How Failovers are Handled for Layer 2 Multicast over MCT

The following failover scenarios may occur. Refer to MCT Failover Scenarios for other types of failover scenarios.

• Local CCEP down event:
  • Outgoing traffic on the local CCEP will now go through the ICL and out of the remote CCEP.
  • Incoming traffic on the local CCEP will now ingress through the remote CCEP, and then ingress through the ICL locally.
• Local CCEP up event:
  • Outgoing traffic on a remote CCEP (after egressing through the local ICL) will now start going out of the local CCEP.
  • Incoming traffic from a client through the ICL (after ingressing on remote CCEP) will now switch back to the local CCEP (this is true only if the client trunk hashing sends the traffic toward the local CCEP).
• CCP (Cluster communication protocol) down event:
  • All related information (IGMP or MLD group, mcache, dynamic router port, PIM-SM snooping entry) that was synced from the peer device will now be marked for aging locally.
• CCP (Cluster communication protocol) up event:
  • All related information (IGMP or MLD group, mcache, dynamic router port, PIM-SM snooping entry) that was learned locally will be synced to the peer device.