> ## 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 Versa Secure SD-WAN
> This help topic describes how to create a VXC from an MVE to Cloud Partners and integrate the connection with Versa Secure 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 = ;
return caption ?
{img}
{caption} : img;
};
export const InlineImage = ({src, alt, height = 16, shadow, width}) => {
const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: InlineImage -';
if (typeof src !== 'string') {
src = String(src);
}
if (!src || src === 'undefined') {
console.error(`${errorPrefix} \`src\` is required — rendering an empty string instead`);
return <>;
}
if (typeof alt !== 'string') {
alt = String(alt);
}
if (alt === 'undefined') {
console.error(`${errorPrefix} \`alt\` is required (use "" for decorative images) — rendering an empty string instead`);
return <>;
}
if (height) {
height = height.toString().replaceAll(/\D/g, '');
}
if (width) {
width = width.toString().replaceAll(/\D/g, '');
}
return ;
};
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 Versa Secure 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/versa/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 an interface in Versa Director
1. Log in to Versa Director.
2. Select the **Workflows** tab in the top menu bar.
3. Select Template > Templates in the left menu bar.
4. Select the template associated with this device.
5. Select the **Interfaces** tab.
6. Under WAN Interfaces, click (Add) to add a subinterface.
7. In the **VLAN ID** field, enter the VLAN value from the Megaport Portal.\
Specify the A-End VLAN for the connection - click the details icon for the connection in the Portal to find this value.
8. In the Network Name column, choose **+ Create WAN Network** from the menu.\
Or select a previously created network, if appropriate.
9. For a new network, enter a name and optionally, a description.
10. Click **OK**.
11. In the IPv4 column, choose **Static** from the menu.
12. Select the **Routing** tab.
13. In the BGP section, select the network created earlier.
14. Enter in the following values for your connection:
* **Local AS** -- The AS value for the A-End of the connection.
* **Neighbor IP** -- The IP address of the B-End of the connection (cloud provider, port, or other MVE).
* **Peer AS** -- The AS value for the B-End of the connection.
* Optionally, enable BFD.
15. Click (Add).
16. Click **Recreate** at the bottom of the page.\
A screen appears that highlights the differences in the configuration.
17. Click **Deploy**.
18. Select the **Configuration** tab in the top menu bar.
19. Select Templates > Device Templates in the horizontal menu bar.
20. Click the template you want to modify.
21. In the side navigation, select Interfaces.
22. Click the vni-0/0 interface.
23. Click the VLAN value of the new subinterface.
24. In the Static Address section, click (Parameterize) to use a variable for the static IP address value. (This is enabled by default.)\
When parameterized, the icon is green. Click it if you need to change it. The parameterized field ensures each device associated with the template has a unique variable for the IP address.
25. Click **OK** two times to update the VNI.
26. In the side navigation, select Virtual Routers.
27. Click the Transport-VR link for your network.
28. In the side navigation, select BGP.
29. Click the Instance ID for your network.
30. Click (Parameterize) to use variables for the Router ID and the Password fields.
31. Click **OK** two times to return to the main window.
#### Step 5: Configure the device
1. Select the **Workflows** tab in the top menu bar.
2. Select Devices > Devices in the left navigation.
3. Click the device to modify.
4. Select the **Bind Data** tab.
5. Enter the values for Static Address, BGP Password, and BGP Router ID.\
Other values, such as the Local and Peer AS are auto-populated from our earlier settings.
6. Click **Deploy**.
7. In the upper right of the screen under your username, click **Commit Template**.
8. Select your **Organization** and **Template**.\
In the lower part of the screen, the Template State will be OUT-OF-SYNC.
9. Click the eye icon in the Differences column.\
A page appears that highlights the differences in the configuration.
10. If you are satisfied with the configuration, click **Commit to Device**.
#### Step 6: Validating your connection
You can review device status, including the connection state, from the Monitor tab in Director.
1. Select the **Monitor** tab in the top menu bar.
2. Select Devices in the horizontal menu bar.
3. Click the device to review status and activity.