Pshem Kowalczyk wrote:
I think that you're missing one other possibility (which may or may not suit you) - putting all of your routing into vrfs and doing the normal leaking between the vrfs. This way you can retain the level of granularity you want (any particular interface might be either in the vrf that has only the 'public' internet or in the 'special' vrf, that has access to the premium routes).
This is the most flexible with regard to import/export and route map control, but of course requires iBGP to work. It is very straightforward relative to VRF internal routing, but I've not yet tried meshing this with eBGP. Still a little paranoid there and haven't "peered" my VRF-aware iBGP even with an internal iBGP peer.
Can you leak defaults between VRFs? (Haven't actually tried that one either...)
Jeff _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
