Dell PowerSwitch S4128F-ON EMC SmartFabric OS10 User Guide Release 10.5.1 - Page 578

Static route leaking Route leaking enables routes that are configured in a default or non-default VRF instance to be made available to another VRF instance. You can leak routes from a source VRF instance to a destination VRF instance. The routes need to be leaked in both source and destination VRFs to achieve end-to-end traffic flow. If there are any connected routes in the same subnet as statically leaked routes, then the connected routes take precedence. In static route leaking, DHCP functionality does not work for overlapping subnets. For example, if two interfaces on different VRFs are on the same subnet and are configured with the same DHCP server, then only one of those interfaces gets an IP address. The other interface does not get an IP address because the client requests from the two interfaces have the same MAC and subnet addresses. The server does not have any unique parameter to differentiate that the request is from two different clients. Limitations ● In VLT scenarios, the resolved ARP entry for the leaked route is not synchronized between the VLT peers. The ARP entry resolved in the source VRF is programmed into the leaked VRF when the leaked route configuration is active. ● During downgrade from 10.4.2, the leaked route configuration is restored. However, the routes remain inactive in the destination VRF instance. ● During downgrade from 10.4.2, the update-source-ip command is not restored. Configuring static route leaking To configure static route leaking: 1. Enter the interface in the source VRF instance that contains the static routes that you want to leak. interface interface-name CONFIGURATION Mode 2. In INTERFACE CONFIGURATION Mode, assign the interface to the source VRF instance. ip vrf forwarding vrf1 INTERFACE CONFIGURATION Mode 3. Assign an IP address to the interface. ip address ip-address VRF CONFIGURATION Mode 4. Enter the interface of the VRF instance to which you want to leak the static routes. interface interface-name CONFIGURATION Mode 5. In INTERFACE CONFIGURATION Mode, assign the interface to the destination VRF instance. ip vrf forwarding vrf2 INTERFACE CONFIGURATION Mode 6. Configure the static route that you want to leak on the destination VRF instance. ip route vrf dest-vrf-name route nexthop-interface 7. Configure the static route that you have configured earlier in the source VRF instance to be available in the destination VRF instance also. ip route vrf src-vrf-name route nexthop-interface OS10(config)#interface ethernet 1/1/1 OS10(conf-if-eth1/1/1)# ip vrf forwarding VRF1 OS10(conf-if-eth1/1/1)# ip address 120.0.0.1/24 OS10(config)#interface ethernet 1/1/2 OS10(conf-if-eth1/1/1)# ip vrf forwarding VRF2 OS10(conf-if-eth1/1/1)# ip address 140.0.0.1/24 OS10(config)#ip route vrf VRF1 140.0.0.0/24 interface ethernet 1/1/2 OS10(config)#ip route vrf VRF2 120.0.0.0/24 interface ethernet 1/1/1 The following example shows the show output: 578 Layer 3