Choose one of the topics below for SD-WAN Resources to help you on your journey with SD-WAN
This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC!
We will not comment or assist with your TAC case in these forums.
we have production environment where we have deployed cool technology SDWAN (it indeed cool).
Even after creating this topic , I have played a bit. And found solution.
Solution is simple, not to use any tloc-action (which results strict tloc-action),but in TLOC list add all TLOCs (both intermediate and ultimate destination). Preference will be based on TLOC preference value which is sent while route is advertised.
Sorry, SDWAN, you indeed better than DMVPN
Kindly ask to moderators not delete topic, may be it will be useful for someone else.
Sorry I've noticed your post too late. Indeed "set tloc-list" is an option here for your task. Just want to ask you to be careful with "set tloc-list", typical pitfall is also described in our SD-WAN troubleshooting tech notes: https://www.cisco.com/c/en/us/support/docs/routers/sd-wan/214502-inappropriate-usage-of-policy-action-se.html
thank you for your comment. Kindly ask to re-read the topic. I already described that tloc-action with backup will not work due to different colors from source to intermediate and from intermediate to ultimate nodes.
Link provided by you describes another case where both devices announce route. In our case only one site announces route.
Btw, I already shared solution I found.
Hi Kanan, yes I understand, I was rather referring to the following:
> but in TLOC list add all TLOCs (both intermediate and ultimate destination)
I haven't seen your policy, just guessing, but "set tloc-list" usually considered dangerous if improperly applied, this is the key message.