Users Guide
4. Configure the import target in VRF-red.ip route-import 1:1
5. Configure the export target in VRF-red.ip route-export 2:2
6. Configure VRF-blue.ip vrf vrf-blue ip vrf forwarding vrf-blue ip address x.x.x.x
255.x.x.x
A non-default VRF named VRF-blue is created and the interface 1/12 is assigned to it.
7. Configure the import target in VRF-blue.ip route-import 1:1
8. Configure the export target in VRF-blue.ip route-export 3:3
9. Configure VRF-green.ip vrf vrf-green ip vrf forwarding VRF-green ip address
x.x.x.x 255.x.x.x
A non-default VRF named VRF-green is created and the interface 1/13 is assigned to it.
10. Configure the import target in the source VRF VRF-Shared for reverse communication with VRF-red
and VRF-blue.ip vrf vrf-sharedip route—import 2:2ip route-import 3:3
The show run output for the above configuration is as follows:
ip vrf VRF-Red
ip route-export 2:2
ip route-import 1:1
!
ip vrf VRF-Blue
ip route-export 3:3
ip route-import 1:1
!
ip vrf VRF-Green
!
ip vrf VRF-shared
ip route-export 1:1
ip route-import 2:2
ip route-import 3:3
Show routing tables of all the VRFs (without any route-export and route-import tags being configured)
Show routing tables of VRFs( after route-export and route-import tags are configured).
Important Points to Remember
• If the target VRF conatins the same prefix as either the sourced or Leaked route from some other VRF,
then route Leaking for that particular prefix fails and the following error-log is thrown.
SYSLOG (“Duplicate prefix found %s in the target VRF %d”, address,
import_vrf_id) with
The type/level is EVT_LOGWARNING.
• The source routes always take precedence over leaked routes. The leaked routes are deleted as soon
as routes are locally learnt by the VRF using other means.
• For recovery, you must take appropriate action either by deleting the unwanted prefixes or issuing
clear command or both.
• In the target VRF, you cannot leak routes that are imported through the route leaking feature.
• The leaked route points to the next-hop of the source routes. You cannot do any modifications to the
next-hop of the leaked route in the destination VRF.
• IPv6 link local routes will never be leaked from one VRF to another.
1064
Virtual Routing and Forwarding (VRF)