The RD is simply meant to distinguish between routes, not VPNs. You CAN
use it on a per-VPN basis, but in the event you are receiving the same
route from multiple places within a single VRF and want to employ any
controlled decision-making on which way to go, you'll want to separate
them (different RD) even though they may be within the same RT!
The RT is merely an extended community value that travels with the
route. You decide to import them to a VRF based on your
policy/configuration. So yes, you can influence based on that.
HTH,
Scott
William Jackson wrote:
Hi guys
Can someone clarify something for me:
The Route distinguisher is the VPN instance identifier correct?
So it is unique per VPN in the network.
And the route target/vrf target is a value that you can assign to
prefixes when advertised from local PE router to limit which remote PE
routers in the VPN will accept the prefixes?
Is this correct?
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
