There is a possibility of a loop occurring due to the Edge of the eHA [enhanced HA] configuration.
The reason is that Edges with eHA configuration forward the unicast packet not destined to their MAC address from Standby device link to Active device link.
This issue occurs in the below condition.
In above case, Edges forward the unicast packet from Standby device link to Active device link with decreasing TTL. If there are two or more similar Edges in the L2 network, this traffic will from a Layer 3 loop.
Velocloud SDWAN, VMware SDWAN, eHA, Enhanced HA
This issue is caused by known software issue #132004. Essentially, Edges should not forward the unicast packet not destined to their MAC address, should drop. The devices running software version 4.5.1.x and 5.0.x.x are susceptible to this issue.
This defect is fixed in 5.2.4.0 and later.
For more information please see VMware SD-WAN Software Upgrade FAQs
Edges are supported the design which multiple links connect to the same network subnet.