Troubleshooting Inter VRF Route Leaking
InertVRF route leaking is not working in ArubaOS-CX switches.
InterVRF route leaking is configured as follow:
- Create two VRF
# vrf RED
# vrf BLUE
- Attach the VRFs to the VLANs
# interface vlan10
#vrf attach RED
# ip address 10.10.10.1/24
# interface vlan20
# vrf attach BLUE
# ip address 220.127.116.11/24
- Leak the routes of one VRF in another
# ip route 18.104.22.168/24 vlan20 vrf RED << Route Leak
# ip route 10.10.10.0/24 vlan10 vrf BLUE << Route Leak
- Check the configuration, above mentioned configuration of route leak looks good, but still InterVRF routing is not working.
- Check if the VLAN is Up or not, when verified that vlan was not up. but before configuring InterVRF routing on the switch, vlan was up and ports were assigned to it.
- whenever we make any changes to the VRF, or attach the vlan to any VRF, that Vlan will loose its configured IP address
- Hence everytime we make changes in VRF, we will not be able to ping vlan's IP which was configured initially but its not present on the switch anymore.
- we need to configure IP address on that vlan again to get it working.
Best practice while configuring InterVRF route leaking is to first map the VLAN to the vrf and then do all the vlan specific configuration.
Attach the VLANs to VRF then assign IP to the VLANs
vrf attach RED
ip address 10.10.10.1/24
vrf attach BLUE
ip address 22.214.171.124/24
Map VLAN to interfaces
interface lag 1
vlan trunk native 1 tag
vlan trunk allowed 10,20
lacp mode active
Leak the routes
ip route 126.96.36.199/24 vlan20 vrf RED << Route Leak
ip route 10.10.10.0/24 vlan10 vrf BLUE << Route Leak