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

Forwarding entries for PIM-SM and PIM6-SM multicast snooping
Table 30 and Table 31 list the forwarding entries for PIM-SM and PIM6-SM multicast snooping.
Forwarding entries (*,G) a TABLE 30
Event MCT-1 MCT-2
No-Join (*,G)->blackhole (*,G)->blackhole
(S,G) Join on (MCT-1) CEP (*,G)->CEP [s] b (*,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]
a.) *ICL: The ICL port is added as default whenever CCEP is in OIF. The data traffic received from the ICL port will be filtered out by
egress filters dynamically programmed on CCEPs.
b.) [s]: denotes sources maintained on port hash-list.
Forwarding entries (S,G) a TABLE 31
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
a.) *ICL: The ICL port is added as default whenever CCEP is in OIF. The data traffic received from the ICL port will be filtered out by
egress filters dynamically programmed on CCEPs.
Forcing a port up in a basic MCT configuration
In a static trunk environment, Preboot eXecution Environment (PXE) images are too small for most
operating systems to leverage LACP during the boot process. As a result, during a PXE build process,
traffic sent by the server is dropped, and the build process can fail.
To correct this situation, a port on an ICX 6650 device connected to a server that is configured as an
MCT client can be set to a “force-up” state so that even if the LACPDU is not received from the server,
the connected port is up and forwards packets.
Forwarding entries for PIM-SM and PIM6-SM multicast snooping
FastIron Ethernet Switch Platform and Layer 2 Switching Configuration Guide 181
53-1003086-04