[c-nsp] Sanely leaking a locally sourced default route from one VRF into another

[Jason Lixfeld]

On 2012-12-12, at 4:36 AM, Adam Vitkovsky <adam.vitkovsky at swan.sk> wrote:

>> I've leaked the default from inet into resi using a combination of 'import
>> route-target' statements and 'import map' statements on the PEs as required.

> I believe the easiest solution is as follows.  
> On the RR PE that originates the default route configure vrf resi. 

This is already the case.  I guess that wasn't clear from my original post?

> Than create a static default route in that vrf resi and for the next hop,
> use the interface that points to internet and IP of the eBGP neighbor (you
> can use tracking next-hop and floating static backup default route). 
> Than advertise the static via MP-BGP to all other PEs with vrf resi. 

Except I have 4 upstream connections on that router and statically routing to any one of them is a potential risk for blackholing traffic if said upstream goes down.

> There should be a mechanism to accomplish extranet vpn on destination PEs as
> well -but I'm not sure how would I accomplish that. 
> We should be looking for some articles regarding extranet vrfs
> I'd love to hear any ideas.