Configuration Guide User guide

FastIron Configuration Guide 853
53-1002494-02
Layer 2 behavior with MCT
22
• Both MCT1 devices must run pimsm-snoop.
• PIM messages are forwarded by way of 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
and ages out if not refreshed.
Forwarding entries for PIM-SM multicast snooping
Table 144 and Table 145 list the forwarding entries for PIM-SM multicast snooping.
TABLE 144 Forwarding entries (*,G)
a
a. *ICL: The ICL port is added as default whenever CCEP is in OIF. The data traffic receiving from ICL port
will be filtered out by egress filter (dynamically programmed) on CCEPs.
Event MCT-1 MCT-2
No-Join (*,G)->blackhole (*,G)->blackhole
(S,G)Join on (MCT-1)CEP (*,G)->CEP [s]
b
b. [s]: denotes sources maintained on port hash-list.
(*,G)->ICL [s]
(S,G)Join on (MCT-2)CEP (*,G)->ICL [s] (*,G)->CEP [s]
(S,G)Join on
(MCT-1)CCEP
(*,G)->CCEP [s], ICL [s] (*,G)->CCEP [s], ICL [s]
(S,G)Join on
(MCT-2)CCEP
(*,G)->CCEP[s], ICL [s] (*,G)->CCEP [s], ICL [s]
TABLE 145 Forwarding entries (S,G)
a
a. *ICL: The ICL port is added as default whenever CCEP is in OIF. The data traffic receiving from ICL port
will be filtered out by egress filter (dynamically programmed) on CCEPs.
Event MCT-1 MCT-2
No-Join (S,G)->blackhole (S,G)->blackhole
Join (MCT-1)CEP (S,G)->CEP (S,G)->ICL
Join (MCT-2)CEP (S,G)->ICL (S,G)->CEP
Join (MCT-1)CCEP (S,G)->CCEP, ICL (S,G)->CCEP, ICL
Join (MCT-2)CCEP (S,G)->CCEP, ICL (S,G)->CCEP, ICL