Static Routing - IP SLA Track for Tunnel using Front Door VRF

[SoloRocky]

I have an interesting problem with IP SLA tracking. Here is the scenario:

- Two static routes, primary and default

ip route vrf MAIN 0.0.0.0 0.0.0.0 10.10.10.2

ip route vrf MAIN 172.12.12.0 255.255.255.248 tunnel50 

- Tunnel 50

Int Tunnel50

vrf forwarding MAIN

ip add 192.168.1.1 255.255.255.252

tunnel source loopback7

ip tcp adjust-mss 1360

tunnel destination 10.20.20.2

tunnel vrf WAN

- Adding IP SLA for primary path using Tunnel 50

ip sla 2023

icmp-echo 10.20.20.2 source-int vlan 201

freq 5

vrf WAN

track 2023 ip sla 2023

- Adding tracking to static route for tunnel

ip route vrf MAIN 172.12.12.0 255.255.255.248 tunnel50 track 2023

- The Problem

Tunnel VRF is MAIN and so is the static route to the tunnel. However, ip sla uses VRF WAN. I haven't found any documentation to show this will work

This is on ASR 1001x with IOS-XE and I don't have a testbed. I can think of using route leaking between VRFs MAIN and WAN but want to if  anyone implemented this.

[paul driver]

Hello

Your ipsla is polling an address in a different VRF than the static route you wish to track so it will not work your need to track within the same VRF

[Anil-Verma-1]

This is chicken and egg 

Tunnel50 is in vrf MAIN

IP SLA has to use vrf WAN and source-int also in vrf WAN

Try this:

- Use vrf MAIN for ip sla - this is needed to ensure track 2023 can use ip sla 2023

- route leak 10.20.20.2 and vlan 201 from vrf WAN to vrf MAIN

[MHM Cisco World]

@SoloRocky  please confirm if this issue solve or not 
thanks 
MHM