Private Overlay using VPLS with SD-WAN reachability

Products

• VMware SD-WAN by VeloCloud

Issue/Introduction

• To provide a workaround when establishing VCMP over private L2 underlay.

Symptoms:

• When building VCMP tunnel towards public VCG over private L2 underlay (VPLS), tunnel is not established.

 

• debug.py
• (…)
• "path": {
•       "gateway": "104.193.31.36",
•       "interface": "GE4",
•       "ipAddress": "172.16.0.1",
•       "logicalId": "jnc1e:25:76:af:e3:0000",
•       "peer_name": "vcg88-cri7",
•       "tunnelingMode": "DEFAULT",
•       "version": "97370453"
•     },
•     "pathState": "ACTIVE",
•     "pathStateRx": "INITIAL",
•     "pathStateTx": "INITIAL",
• (…)

Environment

VMware SD-WAN by VeloCloud

Cause

• Misconfiguration. Since VPLS technology is L2, Velocloud devices appear as directly connected within same LAN. Using Velocloud DC hub as next hop for establishment of overlay for SD-WAN reachability will cause the Overlay tunnel is not established to the public VCG or partner gateway. VCE cannot establish VCMP using another VCE as transit.

Resolution

• When setting up the next hop for a private overlay under WAN settings, you need to specify a non Velocloud device as a next hop.
• 
• 

Additional Information

Impact/Risks:

• VCMP tunnel will not come up, unable to report to VCO over private interface.