[c-nsp] mvrf leaking

[Rodney Dunn]

I don't *think* so. I think to get traffic from the VRF's you need MVPN 
Extranet support:

http://www.cisco.com/en/US/docs/ios/12_2sb/feature/guide/extvpnsb.html

Rodney



Tim Durack wrote:
> Anyone know if an mvrf can be "leaked" across several vrfs?
> 
> ip vrf mvpn-cus1
>  rd 10.0.0.1:201
>  route-target export 65000:201
>  route-target import 65000:201
>  route-target import 65000:202
>  mdt default 239.1.1.1
> !
> ip vrf mvpn-cus2
>  rd 10.0.0.1:202
>  route-target export 65000:202
>  route-target import 65000:202
>  route-target import 65000:201
>  mdt default 239.1.1.1
> !
> 
> Cisco doc says:
> 
> "When configuring the default MDT, note the following information:
> •The group_address is the multicast IPv4 address of the default MDT
> group. This address serves as an identifier for the MVRF community,
> because all provider-edge (PE) routers configured with this same group
> address become members of the group, which allows them to receive the
> PIM control messages and multicast traffic that are sent by other
> members of the group.
> •This same default MDT must be configured on each PE router to enable
> the PE routers to receive multicast traffic for this particular MVRF."
> 
> Which makes me think it might work...
> 
> Tim:>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/