Users Guide

purpose, routes corresponding VRF-Shared routes are leaked to only VRF-Red and VRF-Blue. And for reply, routes corresponding to
VRF-Red and VRF-Blue are leaked to VRF-Shared.
For leaking the routes from VRF-Shared to VRF-Red and VRF-Blue, you can congure route-export tag on VRF-shared (source VRF,
who is exporting the routes); the same route-export tag value should be congured on VRF-Red and VRF-blue as route-import tag
(target VRF, that is importing the routes). For a reply communication, VRF-red and VRF-blue are congured with two dierent
route-export tags, one for each, and those two values are congured as route-import tags on VRF-shared.
To congure route leaking, perform the following steps:
1. Congure VRF-shared using the following command:
ip vrf vrf-shared
interface interface-type slot/port
ip vrf forwarding vrf-shared
ip address ip—address mask
A non-default VRF named VRF-Shared is created and the interface 1/4 is assigned to this VRF.
2. Congure the export target in the source VRF:.
ip route-export 1:1
3. Congure VRF-red.
ip vrf vrf-red
interface-type slot/port
ip vrf forwarding VRF-red
ip address ip—address mask
A non-default VRF named VRF-red is created and the interface is assigned to this VRF.
4. Congure the import target in VRF-red.
ip route-import 1:1
5. Congure the export target in VRF-red.
ip route-export 2:2
6. Congure VRF-blue.
ip vrf vrf-blue
interface-type slot/port
ip vrf forwarding VRF-blue
ip address ip—address mask
A non-default VRF named VRF-blue is created and the interface 1/12 is assigned to it.
7. Congure the import target in VRF-blue.
ip route-import 1:1
8. Congure the export target in VRF-blue.
ip route-import 3:3
9. Congure VRF-green.
ip vrf vrf-green
interface-type slot/port
950
Virtual Routing and Forwarding (VRF)