Configuration Guide User guide

852 FastIron Configuration Guide
53-1002494-02
Layer 2 behavior with MCT
22
IGMP/MLD snooping behavior on MCT cluster devices
• Local information is synchronized to the MCT peer device using CCP. The information includes
Mcache/FDB entry (on arrival of data traffic), joins/leaves, dynamic router ports, and PIM-SM
snooping joins/prunes.
• Native control packets (joins/leaves) that are received are processed by protocol code, and
also forwarded out if required.
• All control/data traffic is received on ICL. The traffic is forwarded out of CCEP only if the remote
CCEP is down; otherwise, it is dropped by the egress filters on CCEP.
• ICL is added as OIF by default whenever the CCEP is involved as either source or receiver. This
provides faster convergence during MCT failover.
• For IGMP/MLD joins/leaves:
• The control packets only received on CCEP are synced to the MCT peer using CCP.
• The control packets received on CEP are not synced to MCT peer using CCP.
• Static groups and static router ports configured on 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.
MCT failover handling for Layer 2 multicast over MCT
The following failover scenarios may occur. Refer to “MCT failover scenarios” on page 843 for other
types of failover scenarios.
• Local CCEP Down EVENT:
• Outgoing traffic on local CCEP will now go through ICL and out of the remote CCEP.
• Incoming traffic on local CCEP will now ingress through the remote CCEP, and then ingress
through ICL locally.
• Local CCEP Up EVENT:
• Outgoing traffic on remote CCEP (after egressing through local ICL) will now start going out
of local CCEP.
• Incoming traffic from client through ICL (after ingressing on remote CCEP) will now switch
back to local CCEP (this is true only if the client trunk hashing sends the traffic towards
local CCEP).
• CCP (Cluster communication protocol) Down EVENT:
• All related information (i.e. IGMP/MLD group, mcache, dynamic router port, pim-sm
snooping entry) that were synced from the peer device will now be marked for aging locally.
• CCP (Cluster communication protocol) Up EVENT:
• All related information (i.e. IGMP/MLD group, mcache, dynamic router port, pim-sm
snooping entry) that were locally learned will be synced to the peer device.
PIM-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 not supported.
• 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.