Issue occurs after gateway reboot. Gateway will lose dce_ip_addr info which is the hub's WAN link address. Under this issue state, spoke will not able to get dce_ip_addr from gateway. As the result overlay tunnel can not be formed from spoke to hub.
VeloCloud VMware SD-WAN all supported gateway releases.
Issue is found on special network configuration described as below :
- SD-WAN overlay network is on top of MPLS network only. VCO public interface and gateway public interface are connected on MPLS network, no public internet connection.
- Hub edge's WAN interface only has address which is under RFC-1918 private address range.
- MPLS routing provides reachability from edge to gateway, NAT to public address is not required.
- Hub edge's WAN link type is configured as User-Defined Public. SD-WAN reachability option is disabled.
- The architecture treats the MPLS WAN link as public to use.
This is not a valid configuration.
In order for WAN link with private address to reach gateway's public interface, NAT to public address has to be implemented, or configure the WAN link as private and enable SD-WAN Service Reachable option.
Workaround:
Option1: Restart hub's service.
Option2: Configure the hub WAN link from wired to wireless and then wireless to wired again.
Permanent Fix:
Correct the configuration
1. Configure hub edge's WAN link type as User-Defined Private and enable SD-WAN Service Reachable option.
2. For spoke edges which need to form tunnel with hub private WAN link, the spoke edges' WAN link should also be configured as User-Defined Private and enable SD-WAN Service Reachable option.
SD-WAN Service Reachability via MPLS
https://techdocs.broadcom.com/it/it/vmware-sde/velocloud-sase/vmware-velocloud-sd-wan/5-2/sd-wan-administration-guide/configure-edge-device-settings-a-roadmap-admin/configure-interface-settings-for-edges-with-new-orchestrator-ui-admin/sd-wan-service-reachability-via-mpls-admin.html