Use the following basic procedure to configure dynamic Inter-VRF route leaking.
About this task
Important
Dynamic inter-VRF route leaking is a feature that should be deployed only by an advanced user.
Note
Note the following limitations and considerations for route leaking:
- Leaked routes will not be leaked again.
- Control plane protocols cannot run on leaked routes.
- Leaking the same prefix across VRFs is not supported. That is, a given prefix can be present in multiple VRFs, but it should not be leaked from one VRF to another. The behavior in such a case will be inconsistent.
Procedure
-
Configure the VRF instances you want to be the leaker (source VRF) and where the route is being leaked to (destination VRF).
-
Specify the interface for the source VRF and map it to the source VRF.
-
Enter the IP address/mask to use for this VRF instance.
-
Specify the interface you want to be the destination VRF and map it to the destination VRF.
-
Specify the IP address/mask to receive the leak.
-
Configure the route map and associated prefix-list.
-
Change the configuration mode to destination VRF address family context. (IPv4 and IPv6 are supported.)
-
Configure the import command, specifying the source VRF and route map to be leaked.
-
(Optional) You can leak BGP or OSPF routes that were learned by the source VRF into the destination VRF. Static routes can also be leaked.