Configuring dynamic inter-VRF route leaking

Use the following basic procedure to configure dynamic Inter-VRF route leaking.

About this task

Important

Important

Dynamic inter-VRF route leaking is a feature that should be deployed only by an advanced user.
Note

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

  1. Configure the VRF instances you want to be the leaker (source VRF) and where the route is being leaked to (destination VRF).
  2. Specify the interface for the source VRF and map it to the source VRF.
  3. Enter the IP address/mask to use for this VRF instance.
  4. Specify the interface you want to be the destination VRF and map it to the destination VRF.
  5. Specify the IP address/mask to receive the leak.
  6. Configure the route map and associated prefix-list.
  7. Change the configuration mode to destination VRF address family context. (IPv4 and IPv6 are supported.)
  8. Configure the import command, specifying the source VRF and route map to be leaked.
  9. (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.