The private virtual interface allows vMotion, ESXi management, management appliance, and workload traffic to flow over the Direct Connect connection between your on-premises environment and your SDDC.
Create one virtual interface for each Direct Connect link you want to make to your SDDC. For example, if you want to create two Direct Connect links for redundancy, create two virtual interfaces.
Each private virtual interface allows you to expose up to 16 logical segments to your on-premises infrastructure.
- Ensure that you meet the prerequisites for virtual interfaces as described in Prerequisites for Virtual Interfaces.
- Log in to the AWS Console and complete the Creating a Hosted Private Virtual Interface procedure under Create a Hosted Virtual Interface.
When the interface has been created, the AWS console reports that it is ready for acceptance.
- For the Interface Owner field, use the account shown in the AWS Account ID field of the Direct Connect page of the Networking & Security tab.
- Select Auto-generate peer IPs and Auto-generate BGP key.
- In the VMC Console, select and accept the virtual interface by clicking ATTACH.
Before it has been accepted, a new VIF is visible in all SDDCs in your organization. After you accept the VIF, it is no longer visible in any other SDDC.It can take up to 10 minutes for the BGP session to become active. When the connection is ready, the State shows as Attached and the BGP Status as Up.
- (Optional) Configure a route-based VPN as backup to Direct Connect
In the default configuration, traffic on any route advertised over BGP by both DX and a route-based VPN uses the VPN by default. To have a route advertised by both DX and VPN use DX by default and failover to the VPN when DX is unavailable, select Use VPN as backup to Direct Connect switch to Enabled.and set theNote: This configuration requires a route-based VPN. You cannot use a policy-based VPN as a backup to Direct Connect.The system requires a minute or so to update your routing preference. When the operation completes, routes advertised by both DX and VPN default to the DX connection, using the VPN only when DX is unavailable.
- Subnet 1 includes routes used by ESXi host vmks and router interfaces.
- Subnet 2 includes routes used for Multi-AZ support and AWS integration
- Subnet 3 includes management VMs
|MGW CIDR||Subnet 1||Subnet 2||Subnet 3|
What to do next
Ensure the vMotion interfaces are configured to use Direct Connect. See Configure vMotion Interfaces for Use with Direct Connect.