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

[Adam Vitkovsky]

>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. 
Right, though you should be able to use next hop availability tracking to
take care of the blackholing issue. 
Unfortunately I didn't find a way how to make ios recursively lookup the
next-hope once the packet was handled by the vrf routing. 
I tried pointing the default towards a loopback interface in the inet vrf
-but that does not work. 
Just a side note -while leaking routes between VRFs you can manually set
next hop with: set ip next-hop recursive vrf inet x.x.x.x . 
-however you need to use the peer's ip address so you're back to square one

Maybe if you are using 7600 you can enable recirculation somehow (not sure
if it's applicable for this scenario though)


adam