Dell MX9116n EMC SmartFabric OS10 User Guide Release 10.5.1 - Page 579

OS10(config)# do show ip route vrf VRF1 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 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. Route leaking using route targets You can leak routes in one VRF instance to another using route targets. NOTE: You can leak routes using route targets only on the default and non-default VRF instance. You cannot leak routes using route targets on the management VRF instance. To leak routes in one VRF instance using route targets: 1. Enter the VRF from which you want to leak routes using route targets. CONFIGURATION ip vrf source-vrf-name 2. Export the route that belongs to one VRF instance. VRF CONFIGURATION ip route-export 1:1 3. Enter the non-default VRF instance to which you want to leak the route. Layer 3 579