Creating a VXC to an MVE Integrated with Cisco SD-WAN
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE).
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. You can connect up to 24 VXCs on a single MVE.
- In the Megaport ONE Portal, choose Networking > Services.
- Select the MVE you want to use. If you haven’t already created an MVE, see Creating an MVE.
- Click Actions and select Add Connection.
The New Connection screen displays the MVE name and A-End details.
Choose Cloud Virtual Cross Connect as your Connection Type.
For specific CSP configuration details:
- AWS Direct Connect – See Creating MVE Connections to AWS.
- Azure Express Route – See Creating MVE Connections to Azure using ExpressRoute.
- Google Cloud – See Creating MVE Connections to Google.
For Oracle and other CSPs, see Creating MVE Connections to Generic Endpoints.
Connecting MVE to MVE
In vManage, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the SD-WAN branch locations connected to these MVEs via the Megaport fabric. For specific configuration details, see Connecting MVEs.
Deleting a VXC
You can terminate a VXC directly from vManage.
To delete a VXC (interconnect connectivity)
In vManage, select Configuration > Cloud OnRamp for Multi-Cloud.
Choose Interconnect Connectivity.
Choose a Megaport ONE account.
Select the interconnect gateway and click the ellipsis (…).