By extending an on-premise network to the cloud, you can roll out migrations in stages, ensuring a minimal downtime. With DC Extensions, you can also preserve your IP and MAC address scheme after migrations.
Verify that the edge has advance gateway networking and VDC network sub interface enabled on vCloud Director.
Verify that you have configured an L2 Appliance.
- In the vSphere Web Client, navigate to .
- In the DC Extensions tab, click New Extensions.
If an L2 Appliance is not configured, you receive an error and must configure an L2 Appliance before you can extend a network.Note:
If you extend a new network from the same on-premise VDC edge to another network on a different cloud-provider VDC-edge, a single on-premise VDC edge is connected to a single cloud provider VDC edge. A new edge and a trunk port group are created, the trunk port group being attached to the new edge.
- Enter a name for the extended network.
- Select a source data center.
- Select a source network.
- (Optional) Select if you want to enable an egress in the source site.
If you select to enable an egress in the source site, the source gateway can forward traffic outside of the extended network.
- Select a Provider cloud.
- Select a target VDC.
- Select a target network.
- (Optional) Select if you want to enable an egress in the target site.
If you select to enable an egress in the target site, the target gateway can forward traffic outside of the extended network.
- Click Start.
Automatic checks are run to verify if L2 VPN gateways exist and vCloud Director Extender creates a port group and deploys a new, standalone NSX Edge appliance.
After the initial configuration processes complete, a new network appears in the DC Extensions tab in a Connected status. For more information about Managing DC Extensions, see Managing DC Extensions.