IP Vrf
VRF-lite works very well in this case. You can use MPLS but then you need to touch every device in the path but with VRF-lite using GRE tunnels you can set this up on just the endpoints.
The VRF part creates path isolation. From the router perspective, two completely separate route tables are maintained and never shall the two meet so to speak. You more or less associate a given interface(s) to the VRF, in this case the tunnel interrfaces and everything including the OSPF process tied to the VRF runs over the isolated path. In fact you can do VRF-based pings, traces, telnets, etc. that will go out the VRF interface rather than going out the standard non-VRF interface.
In a nutshell, think of two physical pathways going into the router and then exiting the router. Both pathways maintain their own routing protocols and routes. In fact both can have their own separate default routes as well. The obvious caveats are that you avoid the typical “gotchas” where tunnel interfaces and dynamic routing protocols are concerned.
A search on CCO for vrf-lite will get you started but here’s a link that you might find useful: //www.cisco.com/univercd/cc/td/doc/product/ong/15400/r46docs/r46mlios/vrf.pd f
Rik
—–Original Message—– From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of ccie-lab Sent: Tuesday, February 05, 2008 9:55 PM To: ccielab@groupstudy.com Subject: IP Vrf
Does anyone have a good explanation or link to describe ip vrf forwarding. I am trying to provide new customer transports through my company ip network running ospf. Can i utlize ip vrf to separate their routing instances or do I need mpls.
Tx
























