08-25-2024 02:22 PM
I have the following scenarion:
Why does the Hub choose vedge2 even though vedge1 is still valid via the TLOC extension? Is there something that can be done to make the Hub prefer vEdge1?
08-25-2024 02:26 PM - edited 08-25-2024 02:36 PM
do you use color strict ?
MHM
08-25-2024 02:54 PM
No. When i turn off the Zone based policy, traffic works. I tried using affinity groups which then forced the hub to use vedge1 as next hop but traffic was still getting dropped when the policy was enabled. I just configured a VRRP tracker which now made vedge2 primary. This works but i was wondering if there was a better way. The whole point of TLOC extension is this vedge1 still can route. Maybe when you have these stateful configurations like ZBFW, tloc extension isn’t good.
08-26-2024 08:34 AM
Can you share topolgy
Thanks alot
MHM
09-12-2024 10:37 AM
Are this issue solved?
If not
Can you run debug packet?
MHM
08-27-2024 06:37 AM
Hi,
which version do you use? Is it vedge or cedge (ios xe)? The problem is most likely due to routing. You need to check omp route result for LAN subnets of VRRP site to understand to which it is failovered when ISP1 is down.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide