Virtual Routing and Forwarding (VRF) tables are logically isolated entities that enable multiple VPN’s to share a common core such as Internet while keeping private networks traffic segregated from the Internet traffic.In some cases, we will need to allow global prefixes to be installed in vrf table and vice-versa. Currently this can be done by adding a static route, etc.Customers want a way to dynamically leak routes between global and vrf table. This is accomplished through the new feature BGP Dynamic Route-leaking that provides a flexibility of leaking multiple prefixes using route-policy for import and export.
Dynamic Route leaking feature is introduced to import routes from global/default vrf to non-default vrf and vice-versa.
Basic Configuration CLI
To import from default-VRF to non-default-VRF import, the following configuration is needed:
import from default-vrf route-policy <POLICY_NAME>
To import from non-default-VRF to default VRF, the following configuration is needed:
export to default-vrf route-policy <POLICY_NAME>
Policy is mandatory in both the cases.
1) Import from default-vrf
i) Matching prefix
Configuration on Cisco router
if destination in (22.214.171.124/24) then
address-family ipv4 unicast
import from default-vrf route-policy dyna-route-leak-8-x