All things related to multicast

[Bill Fenner <>]

>
>FR.TEN-155.NET------NL.TEN-155.NET-----------Mcast99
>AS8933                 AS8933               AS6680
>|                                              |
>|                                              |
>|                                              |
>|                                              |
>|                                              |
>FMBONE2(new box)----------fmbone.serveurs-nationaux.jussieu.fr
>AS2200                         AS1717
>
>Before I shutdown MSDP session DE2-FMBONE I checked MBGP routing-
>FR/NL.TEN-155 and Mcast99 preferred routes from AS2200:
>
>Mcast99#sh ip rpf 195.83.118.16
>RPF information for fmbone.serveurs-nationaux.jussieu.fr (195.83.118.16)
>  RPF interface: ATM4/0/0.36
>  RPF neighbor: NL (212.1.195.42)
>  RPF route/mask: 195.83.118.0/24
>  RPF type: mbgp
>  RPF recursion count: 0
>  Doing distance-preferred lookups across tables
>
>So DE2 should have discarded the messages from direct 1717 peering.

If Mcast99 has a direct peering with fmbone, it will accept the SA
messages because SA's are always accepted from the RP itself.  It
will also accept the messages from NL because of the MBGP route.
That only accounts for 2 copies, though, we haven't figured out yet
where the 1000 others came from =)

Do you have any mesh-groups configured?

If you do a unicast traceroute to 195.83.118.16, do you get there or
is there a routing loop?  A unicast loop would explain everything.

  Bill