Filter
Top Products
Configure VRF-lite | Page 23
Dynamic inter-VRF communication explained
3. If VRF red configuration includes*:
ip vrf red
rd 100:1
route-target export 100:1
route-target export 100:2
route-target export 100:3
route-target export 100:4
route-target import 100:5
route-target import 100:6
And if VRF red initially has routes to networks 10.0.0.0/24, 20.0.0.0/24, then each of those
two routes would have multiple extended community attributes (as defined in the route-
target export command configured in the VRF instance) as follows:
10.0.0.0/24 100:1 100:2 100:3 100:4
20.0.0.0/24 100:1 100:2 100:3 100:4
And If VRF shared configuration includes:
ip vrf shared
rd 100:5
route-target export 100:5
route-target import 100:2
And if VRF shared initially has routes to networks 30.0.0.0/24, 40.0.0.0/24, then each of those
two routes would have an extended community attribute applied (as defined in the route-
target export command) as follows:
30.0.0.0/24 100:5
40.0.0.0/24 100:5
Then via BGP IVR, VRF red will end up with the routes:
10.0.0.0/24 100:1 100:2 100:3 100:4
20.0.0.0/24 100:1 100:2 100:3 100:4
(copy)30.0.0.0/24 100:5
(copy)40.0.0.0/24 100:5
And via BGP IVR, VRF shared will end up with the routes:
(copy)10.0.0.0/24 100:1 100:2 100:3 100:4
(copy)20.0.0.0/24 100:1 100:2 100:3 100:4
30.0.0.0/24 100:5
40.0.0.0/24 100:5
*Use of the command route-target export, as per example 3 above, to tag routes in a VRF
instance with ASNs associated with other VRF instances is uncommon in a VRF-lite
environment.