All things related to multicast

[Jan Novak <>]

> RP address?  (I can see how it would create multiple (S,G,RP) messages
> with different RP's, one per misconfigured RP).

Yes, we had several copies (S,G,RPx), (S,G,RPy) per misconfigured
RP - so I misuderstood your "copies".

> 
> Do you know the rest of their MSDP topology?
> 

As far as I know, they use MSDP only towards TEN-155.
They put into operation new MSDP connection I did not know about,
that it is operational:



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.
I am not sure about the set-up between FMBONE and FMBONE2 as Bernard
wanted to have the old connection as backup. I understood from him,
the FMBONE preferred routes from as6680 and FMBONE2 routes from
AS8933 - all this was meant only for one of these connections to
be operational.

Jan