Bhavin shows you how to
migrate your existing virtual interfaces
to Direct Connect connections

Bhavin_0617

I want to migrate or associate my existing virtual interfaces with AWS Direct Connect connections or LAG bundles. How can I do this?

If you have a new AWS Direct Connect connection or link aggregation group (LAG) bundle, you might want to migrate or associate it with your virtual interfaces.

Note: When you migrate or associate an existing virtual interface to a new Direct Connect connection, the configuration parameters that are associated with the virtual interfaces are the same. You can pre-stage the configuration on the Direct Connect connection and then update the BGP configuration.

Follow these instructions to:

  • Migrate an existing virtual interface associated with a Direct Connect connection to a new LAG bundle
  • Migrate an existing virtual interface associated with a LAG bundle to another LAG bundle
  • Migrate an existing virtual interface associated with a Direct Connect connection to another Direct Connect connection

Note: It is best to perform these steps during a scheduled maintenance window to minimize downtime.

Migrate an existing virtual interface associated with a Direct Connect connection to a new LAG bundle

In this example, you have a virtual interface (dxvif-A) that is associated with a Direct Connect connection (dxcon-A) that needs to be migrated or associated with a LAG bundle (LAG-B).

  1. From the Direct Connect console, in the navigation pane, choose LAGs, and select the LAG bundle (LAG-B).
  2. Navigate to the Actions tab and choose Associate Virtual Interface.
  3. In Connection or LAG, choose the bundle that you want to migrate (LAG-B).
  4. In Virtual Interface, choose the virtual interface (dxvif-A), select the agreement checkbox, and then choose Continue.

Note: The virtual Interface will go down for a brief period.

The virtual Interface (dxvif-A) will migrate to the new LAG bundle (LAG-B).

Migrate an existing virtual interface associated with a LAG bundle to another LAG bundle

In this example, the virtual interface (dxvif-B) is active and associated with a LAG bundle (LAG-B) that is associated with another LAG bundle (LAG-C).

  1. From the Direct Connect console, in the navigation pane, choose Virtual Interfaces, and select the virtual interface you want to migrate.
  2. Navigate to the Actions tab and choose Associate Connection or LAG.
  3. In Connection or LAG, change the value to the LAG bundle (LAG-C) that you want to associate with the virtual interface (dxvif-B).
  4. In Virtual Interface, verify that the virtual interface that you want to migrate (dxvif-B) is selected. Select the agreement check box, and then choose Continue.

Note: The virtual interface will go down for a brief period.

The virtual interface (dxvif-B) will migrate to the new LAG bundle (LAG-C).

Migrate an existing virtual interface associated with a Direct Connect connection to another Direct Connect connection

In this example, the virtual interface (dxvif-C) is active and associated with a Direct Connect connection (DX-C). You have another Direct Connect connection (DX-D) that is UP and operational. For more information, see How do I provision an AWS Direct Connect connection?

  1. From the Direct Connect console, in the navigation pane, choose Virtual Interfaces, and select the virtual interface you want to migrate.
  2. Navigate to the Actions tab and choose Associate Connection or LAG.
  3. In Connection or LAG, choose the Direct Connect connection that you want to migrate to (DX-D).
  4. In Virtual Interface, verify that the virtual interface (dxvif-C) is associated with the current Direct Connect connection (DX-C). Select the agreement check box, and then choose Continue.

Note: The virtual interface will go down for a brief period.

The virtual interface (dxvif-C) will migrate to the new Direct Connect connection.


Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center

Published: 2016-08-17