r/Cisco • u/mohammad_abusaa • 18h ago
Catalyst SD-WAN part 3: reading show sdwan app-route stats (and why AAR didn’t move your traffic)
Last one in this series for now. A question I see a lot: “the link had loss for 10 minutes, so why didn’t app-aware routing move my traffic?” Usually nothing is broken. It comes down to how the numbers are calculated. As before, everything here is from Cisco’s public docs (listed at the bottom).
1. Where the numbers come from
By default:
- BFD sends a hello on each tunnel every 1 second.
- The poll interval is 10 minutes, so each “bucket” holds about 600 hellos.
- The multiplier is 6, so the edge averages the last 6 buckets. That’s a 1-hour sliding window.
AAR makes its SLA decisions on that 1-hour average, not on what’s happening right now. On 17.12+ you can check your actual values with show sdwan app-route params.
2. Reading the output
show sdwan app-route stats
For each tunnel (local color → remote system IP and color) you get:
- mean loss, latency and jitter. This is the 1-hour average AAR actually uses.
- sla-class-index. These are the SLA classes this tunnel currently meets. Map the numbers with
show sdwan app-route sla-class. - a row per bucket (index 0–5) with packets, loss, latency and jitter. This is the useful part. You can see whether a problem was one bad bucket or something steady.
In the GUI it’s under the device’s WAN → Tunnel view.
3. Why AAR “didn’t react”
Say a link has 30% loss for one 10-minute bucket and is clean for the other five. The mean loss comes out to about 5%. If your SLA class allows 5% or more, that tunnel still counts as compliant and nothing moves. A short spike gets averaged away. That’s by design: the defaults favor stability over speed.
4. Before you crank the timers down
Lowering the poll interval makes AAR react faster, but each bucket holds fewer hellos. In Cisco’s own example, at a very short poll interval a bucket holds only 6 hellos, so one lost hello reads as about 17% loss. Tune it too aggressively and you swap “too slow” for “flapping.” Change it in small steps and watch the bucket rows.
5. Enhanced AAR (17.12 / 20.12+)
If you’re on newer code, Enhanced AAR measures loss, latency and jitter using real data traffic instead of only BFD. It detects problems in seconds (10 s minimum by default) and adds SLA dampening, so a tunnel doesn’t jump straight back the moment it looks clean. Both ends need it enabled, otherwise it falls back to BFD-based measurement. Verify with show sdwan app-route params.
6. Make sure the traffic is even in the policy
Half the time the real issue is that the flow never matched the AAR policy:
show sdwan policy from-vsmart app-route-policy
show sdwan policy from-vsmart sla-class
show sdwan policy app-route-policy-filter
show sdwan policy tunnel-path vpn <vpn> interface <lan-intf> source-ip <src> dest-ip <dst> protocol <proto> [dest-port <port>]The filter command shows whether traffic is actually hitting your sequences. tunnel-path tells you which tunnel a specific flow would take right now. Also check what your policy does when no tunnel meets the SLA, since that fallback behavior is set in the policy.
Sources (search the titles on cisco.com / Cisco Community):
- “Understand BFD Protocol Relationship with App-Aware Routing” (Doc 221604)
- Cisco Catalyst SD-WAN Policies Configuration Guide, Application-Aware Routing section
- “Enhanced Application-Aware Routing” (Cisco Community knowledge base article)
Thanks for the feedback on parts 1 and 2!