Users Guide

-----------------------------------------------------------------------------------------
-----------
C 120.0.0.0/24 via 120.0.0.1 ethernet1/1/1 0/0 00:00:57
S 140.0.0.0/24 Direct,VRF2 ethernet1/1/2 1/0 00:00:04
OS10(config)# do show ip route vrf VRF2
Codes: C - connected
S - static
B - BGP, IN - internal BGP, EX - external BGP
O - OSPF, IA - OSPF inter area, N1 - OSPF NSSA external type 1,
N2 - OSPF NSSA external type 2, E1 - OSPF external type 1,
E2 - OSPF external type 2, * - candidate default,
+ - summary route, > - non-active route
Gateway of last resort is not set
Destination Gateway Dist/Metric Last Change
-----------------------------------------------------------------------------------------
-----------
S 120.0.0.0/24 Direct,VRF1 ethernet1/1/1 1/0 00:00:05
C 140.0.0.0/24 via 140.0.0.1 ethernet1/1/2 0/0 00:01:54
Configuring source IP address for a leaked route
If the source IP is not mentioned explicitly for any self-originating packet (for example, ping or traceroute) to the leaked route
destined through the parent VRF, the system chooses a source based on its source selection algorithm.
NOTE: For end-to-end traffic to flow, you must specify the source for self-originating packets and leak the same into the
destination VRF.
To mitigate this issue and have control over the source IP address for leaked routes, you can create a loopback interface and
associate it with the leaked VRF.
To explicitly mention the source interface for the leaked VRF:
Enter the following command:
update-source-ip
VRF CONFIGURATION Mode
After you configure the source IP address in a leaked VRF, if ping is initiated without -I option, then the source IP address will be
that of the loopback interface.
Example: Route leaking between VRFs with asymmetric IRB routing
With asymmetric IRB routing, the virtual networks that you configure are present in all the VXLAN tunnel endpoints (VTEPs). If
the DHCP server and client reside in different VRFs within the same or different VTEPs, request from the client does not reach
the server.
In this scenario, the server network must be leaked to the client VRF for the client request to reach the server. The client
network must be leaked to the server VRF for the server reply to reach the client.
In this example, the DHCP client is connected to GREEN VRF in VTEP1 and the server is connected to RED VRF in VTEP 2. The
client is not able to reach the server. The client and server connected networks from the GREEN and RED VRFs must be leaked
to the other tenant VRFs respectively. Route leaking enables server connectivity for hosts connected to different VRFs.
Layer 3
733