Creating an MCR VXC
With a Megaport Cloud Router (MCR) configured, you can add a Virtual Cross Connect (VXC) to a CSP, a local port, or a third-party network. You can optionally connect a physical Port to the MCR via a private VXC.
A VXC (Virtual Cross Connect) is a point-to-point Layer 2 circuit between two endpoints that is mapped with a VLAN ID on each end. You can order VXCs to reach any destination in the Megaport network just like the VXCs used with the physical Ports. You can connect up to 25 VXCs per MCR.
The VXC target destination type determines the peering type. The peering type determines which routes are advertised. For details, see MCR Route Advertisement.
- Select Networking > Services.
- Select an MCR.
- The MCR must be LIVE before you can add a VXC.
- If you haven’t already created an MCR, see Creating an MCR.
- Select Add Connection from the Actions menu.
Select a connection type from the drop-down menu:
- Private Virtual Cross Connect – Connect to other Ports local to the current company account.
After selecting Private Virtual Cross Connect, name the connection (start the name with a letter), select a destination Port (B-End), and select a rate limit that doesn’t exceed the total rate limit for the MCR. Allow enough bandwidth for any connections that you might add later. Optionally, enter an VLAN ID for the B-End.
Cloud Virtual Cross Connect – Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud Virtual Cross Connect, select a provider. Some providers require a service key.
For specific CSP configuration details:
- AWS - See Creating MCR Connections to AWS.
- Azure - See Creating MCR Connections to Azure using ExpressRoute.
- Alibaba - See Creating MCR Connections to Alibaba.
- Google - See Creating MCR Connections to Google.
- Salesforce - See Creating MCR Connections to Salesforce.
- Oracle - See Creating MCR Connections to Oracle.
- IBM - See Creating MCR Connections to IBM.
- SAP - See Creating MCR Connections to SAP HANA.
(Optional) Under Billing Details, enter a Service Level Reference number and a Promo Code, if you have one.
Click Create Connection.
Review the details and click Confirm.
Configuring VXC details
For each VXC connected to an MCR you can configure one or more interfaces, BGP connections, or static routes. Most VXCs will use one interface. However, you can configure multiple interfaces enabling a Q-in-Q connection and specifying an inner VLAN tag for each interface. Each VLAN ID must be unique. You can add up to five VLAN IDs.
Enable or disable the QinQ VLAN option:
- Disabled allows a single VLAN tag (802.1q). This is the default setting. In most cases, you use a single VLAN that is exposed on the destination physical port as a trunked port instance, allowing the port to contain multiple VXCs to destinations other than the MCR you are configuring. Some use cases might require multiple inner VLANs exposed to this port through Q-in-Q.
- Enabled allows the VLAN to carry multiple or dual-stacked VLANs (802.1ad).
After enabling QinQ, you can accept the default VLAN ID or specify the VLAN ID for the connection.
The tag protocol identifier (TPID) will be set to 0x8100.
For details, see Understanding Q-in-Q with Megaport VXCs.
If you have enabled QnQ, click Add VLAN to enter the preferred VLAN ID for the B-End of the connection. Megaport automatically assigns an available VLAN to the B-End. If you enter a VLAN ID, Megaport verifies that the VLAN ID is available.
To configure a VXC interface
- Select Networking > Services.
Select the VXC attached to the MCR.
Select the A-End Configuration tab.
Enter one or more IP addresses and subnet mask to configure on the A-End interface.
Optionally, select a NAT source IPv4 address from the Network Address Translation drop-down list. All packets leaving this interface will have their source NAT rewritten to this address.
Network Address Translation (NAT) allows flexibility in designing a scalable and secure multi-vendor, multi-cloud, or hybrid cloud scenario. Source NAT translates the source IP address of a packet leaving the MCR. When you assign a NAT IP address in MCR, all packets leaving the interface use that IP address as their source IP address. Enable this feature when NAT is required for a connection, for example, when you need to translate several private IP addresses into a single public IP address to meet cloud service provider requirements.
For details on how MCR performs NAT to support public peering types to cloud service providers, see How the MCR performs NAT.
Enter any details specific to the VXC type.