A few months ago, I got a flattering comment from a colleague on Slack: Not…
Before you undertake any network design, you must always consider the business requirements and use cases. Your chosen network design will be largely influenced by the chosen use cases.
VMware Hybrid Cloud Extension delivers secure and seamless app mobility and infrastructure hybridity across vSphere 5.0+ versions, on-premises and in the cloud.
HCX offers bi-directional application landscape mobility and data center extension capabilities between any vSphere version. HCX includes vMotion, Bulk Migration, High Throughput Network Extension, WAN optimization, Traffic Engineering, Load Balancing, Automated VPN with Strong Encryption (Suite B) and secured data center interconnectivity.
This reference architecture document will not delve into all the HCX features but will instead on the standard use cases:
For customers that need to maintain the same IP addresses after they’ve migrated workloads to VMware Cloud on AWS, they can use the NSX Layer 2 VPN functionality.
NSX has offered a L2VPN capability for several years. A L2VPN enables customers to stretch networks between two different sites, over a public or private network (with no requirements on MTU).
VMware Cloud on AWS uses NSX to provide L2VPN features in your cloud SDDC.
In the July 2018 release of VMware Cloud on AWS was introduced Route-based VPN as part of the NSX-T roll-out. Route-Based VPN provides vast improvements from the traditional Policy-Based VPN.