Multicast vrf....

Stumped. What do you check for if you know your config is correct. The rp mappings come through. The "sh ip mroute" verifies the routes. The tunnels are up. All looks good but you cannot ping!?

 

PE routers:

 

ip vrf test

rd 1:1

route-target import 1:1

route-target export 1:1

mdt default 239.0.0.1

!

ip multicast routing vrf test

ip pim vrf test rp-address 192.168.0.1

!

int f0/0

ip add 192.168.2.2 255.255.255.0

ip vrf forwarding test

ip pim sparse-mode

 

Just the ip addresses change per PE device.

 

Thanks

 

James

 

Comments

  • its a dumb solution (i got mixed up before....sorry) - so sorry

     

    but - i had a working network of 50 PE routers (more or less) and some worked and some didn't

     

    what we found is that the MDT did not encapsulate the packets on the PE's that didn't have "ip multicast-routing" even though "ip multicast-routing vrf VRFXXX" was on them

     

    please check just to be sure that it is configured on all PE routers ("ip multicast-routing")...

     

    HTH

    Shai.

     

     

    Stumped. What do you check for if you know your config is correct. The rp mappings come through. The "sh ip mroute" verifies the routes. The tunnels are up. All looks good but you cannot ping!?

     

    PE routers:

     

    ip vrf test

    rd 1:1

    route-target import 1:1

    route-target export 1:1

    mdt default 239.0.0.1

    !

    ip multicast routing vrf test

    ip pim vrf test rp-address 192.168.0.1

    !

    int f0/0

    ip add 192.168.2.2 255.255.255.0

    ip vrf forwarding test

    ip pim sparse-mode

     

    Just the ip addresses change per PE device.

     

    Thanks

     

    James

     

     

Sign In or Register to comment.