An SD-WAN Edge in a data center can act as a Hub to direct traffic to/from branches. The SD-WAN Edge can be used to manage both MPLS and Internet traffic. The Hub in a data center can be configured in a one-arm or two-arm configuration. In addition, a data center can be used as a backup. Datacenter Edge capacity planning must be thoroughly done to enable the datacenter Hubs to handle the number of tunnels, flows and traffic load from branches. Also, the Edge model must be selected accordingly. For more information, consult the VMware Support or Solution Architect team.
The following table describes the various designs with different options, about how SD-WAN Edge can be inserted into the topology:
| Option | Description |
|---|---|
| Hub 1 | Data Center or regional Hub site with SD-WAN Edge deployed in two-arm topology. |
| Hub 2 | Data Center or regional Hub site with SD-WAN Edge deployed in one-arm topology (same interface carries multiple WAN links). |
| Private WAN link(s) only Site | Classic MPLS sites. |
| Hybrid Site-1 | SD-WAN Edge is deployed off-path. SD-WAN Edge creates overlay across both MPLS and Internet paths. Traffic is first diverted to the SD-WAN Edge. |
| Hybrid Site-2 | SD-WAN Edge is deployed in-path as the default gateway. It is always the default gateway. This topology is simpler but makes SD-WAN Edge a single point of failure and may require HA. |
| Public WAN link(s) only Site | Dual-Internet site (one of the links is behind a NAT router). |
Note: These are some common deployment methods used to explain the concept. The Customer topology may not be limited to these methods.
