For an HA setup, auto rollback is done on one edge only and not both edges.

Products

• VMware VeloCloud SD-WAN

Issue/Introduction

For an HA setup, where edge X is the active edge and Y is standby and config changes done for both WAN links to bring the edges down (the config change was wrong WAN IPs and ISP IPs for both links), when the rollback kicks in, only edge X is rolled back to last good config, while edge Y remains with the wrong config.

Environment

Site with HA setup and trying to test the auto rollback feature.

Cause

Issue is tracked under issue #94667
It is confirmed that we don't rollback on the edge that was standby at the time when wrong config was applied.
When the wrong config applied, X came down and failover to Y occurred, then rollback kicks in after few mins, so X after rollback is the standby edge and no longer the active edge.
When checking via CLI, only X has the correct WAN IPs but on Y CLI & GUI still showing the wrong IPs.

Resolution

Engineering working on the fix for now.
But as a workaround, you can either:

- Adjust the config for edge Y from GUI
- or force HA failover from GUI, and accordingly edge Y will become standby and have the good config again.