[c-nsp] VRF-Lite Question

[Shakeel Ahmad]

Thanks Dean & Ray,

It was easy leaking routes from 1 VRF to other due to this doc:

http://www.cisco.com/en/US/tech/tk436/tk832/technologies_configuration_example09186a0080231a3e.shtml

regards,
SA


On 2/12/07, Dean Smith <dean at eatworms.org.uk> wrote:
>
> Although the physical interface is in one VRF - its associated routes can
> be
> in several. Traffic within a VRF will use the interface if it has a route
> "through" it, even if the interface itself is in another VRF.
>
> regards the community - at the simplest level for VRF-Lite if VRF#1
> exports
> routes with community "1" - and you want to have those routes in VRF#2.
> Set
> VRF#2 to import community "1". I believe you need the routes in BGP for
> the
> import/export to work between VRFs.
>
> If you want to be selective about the routes exchanged you need a
> combination of import/export maps.
>
> If you don't want any routes exchanged between VRFs there is no need to
> have
> either an import or export community set. I think one of the more
> confusing
> aspects of some VRF-Lite sample config is that often both import and
> export
> communities are set routinely when there is no need or desire to exchange
> routes between VRFs.
>
> Dean
>
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Shakeel Ahmad
> Sent: 11 February 2007 21:07
> To: Ray Burkholder
> Cc: [c-nsp]
> Subject: Re: [c-nsp] VRF-Lite Question
>
> Thanks, one more question,
>
> In VRF-Lite, there's a case when 2 VRF Interfaced need to route traffic on
> a
> single interface outside - how can the outside interface be part of two
> VRF.
> What community should be exported or imported in which VRF.
>
> thanks,
> SA
>
>
> _______________________________________________
> 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/
>