Crazy about VMware SD-WAN

VMware SD-WAN Enhanced High Availability (HA) is a redundant Edge installation where both Edges have each different WAN networks connected to only one of the 2 devices. When both Edges are online, the standby edge will forward packets between it`s local active WAN circuits to the active edge via the GE1 HA-Link.  One basic rule for the automatic detection of the Enhanced mode is that WAN circuits have to use different WAN Interfaces on that edges.  Here is a working example for Enhanced HA  BR-25 is the Enhanced HA pair with one Internet connection (GE3) and one MPLS connection (GE4)  As I did not know which interface will be used for the MPLS connection, I configured GE4 to GE6 as  User Defined Private WAN Overlay. In that way a local operator can connect the MPLS circuit to any of those 3 WAN Interfaces.     This perfectly works for single Edges and even reconnecting from one MPLS interface to another is completely unproblematic.   Unfortunately...

Configuring different High Availability Features one Branch Setup in my lab was using an MPLS CE-Router and VRRP to allow a restricted Fault Tolerance. When the VMware SD-Wan Edge goes down, there is still a working MPLS connectivity via the CE Router, which means the Branch in that case behaves like a NSD (Non-SD-Wan enabled site) and you need to have a forwarding via either a hybrid Partner Gateway or Hybrid HUB site to still be able to reach all necessary destinations.  The MPLS-facing CE-Router in my case is a Cisco IOS L3 Router, MPLS connectivity for that customer is using OSPF  On the VCO the Edge BR-20 has the corresponding VRRP-setting   GE1 is the Link from Edge to the CE-Router using pt-2-pt OSPF  In the WAN Settings GE1 is marked as User Defined Wan Overlay of type Private Wired named MPLS-Cust-2  The necessary Enable Wan Overlay Flag is correctly set, telling the Edge to also build Overlay tunnels to Gateways using that connection towards MPLS vi...