Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) - Manual (Page 716)

686 Multi-Service IronWare Switching Configuration Guide
53-1003036-02
MCT Snooping
18
MCT remote CCEP up event
CCEP up event from the MCT PEER is generated only if,
• IGMP joins may start coming thru the remote CCEP links or
• IGMP joins may continue to come thru the local CCEP link as before.
In both cases, upon receiving MCT CCEP up event from peer, the local CCEP ports will be removed
from the OIF list of those SG entries with ICL as IIF. No other SG entries are affected. They'll
continue to have the membership information from CCEP ports.
In case2, it will continue to send MDUP join messages (with CCEP flag set) to the MCT peer, as
usual. This will ensure that, in the MCT peer, those SG's sourced from its CEP ports will have its
CCEP links as OIF (efficient path).
Configuration considerations
• IGMP and PIM proxy configurations need to be configured on both the MCT peers.
• Both MCT nodes should have same snooping mode (either both should be active or both
should be passive).
• Static IGMP membership configurations for CCEP ports need to configured on both the MCT
peers.
• Static uplink configurations need to be configured on both the MCT peers.
• MDUP does not support fragmentation of control packets over ICL.
• The IP MTU of any non-Brocade PIM router connected to a Brocade MCT PIM Snooping node
needs to be configured to <=1450 bytes. This is due to the CCP payload size limit.
FIGURE 185 MCT snooping topology example