Brocade FastIron Ethernet Switch Platform and Layer 2 Switching Configuration Guide - Manual (Page 180)

• All control and data traffic is received on the ICL. The traffic is forwarded out of a CCEP only if the
remote CCEP is down; otherwise, it is dropped by the egress filters on the CCEP.
• The ICL is added as outgoing interface (OIF) by default whenever the CCEP is a source or a
receiver. This provides faster convergence during MCT failover.
• For IGMP/MLD joins/leaves:
‐ Only control packets received on a CCEP are synced to the MCT peer using CCP.
‐ Control packets received on a CEP are not synced to the MCT peer.
• Static groups and static router ports configured on a CCEP are not synced across to the MCT peer.
For these features to work correctly, they must be manually configured on the respective CCEP of
both the cluster nodes.
How failovers are handled for Layer 2 multicast over MCT
The following failover scenarios may occur. Refer to MCT failover scenarios on page 170 for other
types of failover scenarios.
• Local CCEP Down EVENT:
‐ Outgoing traffic on local CCEP will now go through the ICL and out of the remote CCEP.
‐ Incoming traffic on 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/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/MLD group, mcache, dynamic router port, pim-sm snooping
entry) that was learned locally will be synced to the peer device.
PIM-SM and PIM6-SM snooping over MCT
• PIM-SM snooping can be configured only on a VLAN. It requires IGMP snooping to be running in
passive mode. IPv6 snooping is supported.
• PIM6-SM snooping can be configured only on a VLAN. It requires MLD snooping to be running in
passive mode.
• Router ports can be configured on a VLAN or globally. They can be learned dynamically on the port
where the query is received or configured statically.
• Both MCT1 devices must run pimsm-snoop.
• PIM messages are forwarded via the hardware.
• PIM join/prune is synced to the peer cluster device using CCP.
• PIM prune is processed only if indicated by the peer cluster device.
• PIM join/prune received natively on ICL is ignored.
• PIM hello is not synced but is received natively on ICL.
• PIM port/source information is refreshed on both cluster devices by syncing PIM messages. The
information ages out if not refreshed.
How failovers are handled for Layer 2 multicast over MCT
180 FastIron Ethernet Switch Platform and Layer 2 Switching Configuration Guide
53-1003086-04