> ## Documentation Index
> Fetch the complete documentation index at: https://docs.megaport.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating MVE Connections to Any Endpoint with Arista VeloCloud SD-WAN

> This help topic describes the general steps to create a VXC from an MVE to a Cloud Service Provider, a Port, or an MCR and integrate the connection with Arista VeloCloud SD-WAN.

export const Image = ({src, alt = '', caption, width, height, shadow}) => {
  const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: Image -';
  if (typeof src !== 'string') {
    src = String(src);
  }
  if (!src || src === 'undefined') {
    console.error(`${errorPrefix} \`src\` is required — rendering an empty string instead`);
    return <></>;
  }
  const img = <img className={['mega-image-style', shadow ? 'shadow' : ''].join(' ')} src={src} alt={alt} width={width} height={height} style={{
    display: 'block'
  }} />;
  return caption ? <figure>
      {img}
      <figcaption style={{
    textAlign: 'center',
    width
  }}>{caption}</figcaption>
    </figure> : img;
};

This topic describes the general steps to configure and deploy a Megaport VXC connection in the Megaport Portal and integrate it with an MVE in Arista VeloCloud SD-WAN. The VXC can connect to a Cloud Service Provider, a Port, or an MCR.

#### Step 1 -- Create an MVE

* Create an MVE in the Megaport Portal.\
  For more information, see [Creating an MVE](/mve/vmware/creating-mve).
  The MVE needs to be in the active state.

#### Step 2 -- Create a VXC from the MVE

1. In the Megaport Portal, select the MVE created in Step 1.
2. Create a VXC to another MVE, a Port, or Cloud Service Provider.\
   For more information, see [Creating a VXC](/connections/overview#create_vxc).
   Ensure both ends of the connection are active and have BGP configured.
3. In the connection details, note the A-End VLAN.

#### Step 3 -- Collect these values for the connection.

* MVE IP address
* MVE VLAN (A-End)
* MVE ASN
* Cloud/B-End IP address
* B-End ASN
* MD5 Password

#### Step 4 -- Create a subinterface in Orchestrator.

1. In Orchestrator, go to Configure > Edges, click the MVE.
2. Select the **Device** tab and scroll down to Interface Settings.
3. Click **+Add Subinterface**.
4. From the **Select Interface** menu, choose GE3 and for the **Subinterface ID** enter the A-End VLAN ID configured for the connection in the Megaport Portal.
5. Change the **Addressing Type** to Static and provide the **IP Address** (MVE), **CIDR value** (MVE), and **Gateway** (Cloud/B-End IP address).
6. Ensure **Enable VLAN Tagging** is enabled.
7. Click \*\*Update GE3:\*\**vlan-id*.
8. In the upper-right corner of the Configure > Edges window, click **Save Changes** and then confirm.
9. Go to Configure > Edges and click the MVE device.
10. Select the **Device** tab and in the Configure Segments section, click **Enable Edge Override** for BGP Settings.
11. Click the toggle button to turn on BGP and click **Edit**.\
    The BGP Editor appears.
12. For **Local ASN**, add the ASN for the MVE side of the connection.
13. For the **Neighbor IP**, add the IP address of the B-End of the connection.
14. Add the B-End ASN to the **ASN** field for the neighbor.
15. View all Additional Options and enable **MD5 Auth** and enter your **MD5 Password** (**BGP Auth Key**).
    <Image src="/images/cloud/mve/vmware/aws/orch-bgp-settings-aws.png" alt="BGP Settings" shadow={true} width={700} />
16. Click **OK** and then click **Save Changes**.

#### Step 5 -- Validating your connection

Under Test & Troubleshoot > Remote Diagnostics, select the MVE and click **Run** for **Troubleshoot BGP - Show BGP Summary** to verify the BGP session and ensure the remote router is up.

You can also check connectivity and BGP status from the CLI of the edge device. For more information, see [Reviewing your VMware MVE connection settings](/cloud/mve/vmware/generic/mve-vxc-details).