All things related to multicast

[Bill Owens <>]

On Thu, Jun 10, 2010 at 08:57:10PM +0300, Zenon Mousmoulas wrote:
> However MSDP peer-RPF check fails: SA  
> announcements are rejected when no prefix matches the RP/Originator,  
> so the default network doesn't apply in this case, or so it seems.

How is the default route created - static, or supplied by the eBGP peer? I 
just tried a quick experiment with an internal router that has a static 
default:


c7609#sh config | incl 0.0.0.0
ip route 0.0.0.0 0.0.0.0 199.109.35.1
c7609#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
c7609(config)#ip mroute 0.0.0.0 0.0.0.0 199.109.35.1
c7609(config)#end
c7609#sh ip rpf 2.3.4.5
RPF information for ? (2.3.4.5)
  RPF interface: GigabitEthernet1/1
  RPF neighbor: nn-3550-ext.nysernet.net (199.109.35.1)
  RPF route/mask: 0.0.0.0/0
  RPF type: static
  RPF recursion count: 0
  Doing distance-preferred lookups across tables
c7609#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
c7609(config)#no ip mroute 0.0.0.0 0.0.0.0 199.109.35.1
c7609(config)#end
c7609#sh ip rpf 2.3.4.5
RPF information for ? (2.3.4.5) failed, no route exists

Seems to indicate that the static mroute works. It would be incorrect in this 
case, since the unicast default route points to our commercial ISP 
connection, and the R&E side is native BGP/mBGP. 

Bill.