Creating a Private VXC

This topic describes how to connect a private VXC (Virtual Cross Connect) to an MCR or Megaport in the Megaport network.

With an MCR or Megaport configured, you can deploy a private VXC to connect to another port local to the current company account. A private VXC is essentially a point-to-point Ethernet connection between an A-End (your Megaport or MCR) and a B-End (the Private VXC destination type). For example, you could create an interconnect within a data center to extend your private network backbone capability, or connect a production data center to a redundant data center for disaster recovery.

To deploy a private VXC

  1. In the Megaport Portal, go to the Services page and select the Megaport or MCR you want to use.

    If you haven’t already created a Megaport or MCR, see Creating a Megaport or Creating an MCR.

  2. Select the originating Megaport (the A-End).

  3. Click +Connection.
    Add Connection

  4. Click Private VXC.

  5. Select the target Megaport (the B-End).

  6. Click Next.

  7. Specify the VXC details:

    • Name your connection - Specify a name for the VXC that is easily identifiable. You can change the name later, if you like.

    • Invoice Reference (optional) - Specify an identifying number for the VXC to be used for billing purposes, such as a purchase order or cost center number.

    • Rate Limit - Specify a rate limit, in Mbps. The maximum speed available is limited to the smallest of the originating or destination port or MCR. The maximum speed is displayed.

    • Preferred A-End VLAN - Specify the 802.1q VLAN tag for this connection for the A-End.

      Each VXC is delivered as a separate VLAN on your Megaport or MCR. This must be a unique VLAN ID on this port and can range from 2 to 4093. If you specify a VLAN ID that is already in use, Megaport will assign the next closest available value. If you don’t specify a value, Megaport will assign one.

    • Preferred B-End VLAN - Specify the 802.1q VLAN tag for this connection that you will receive via the B-End VLAN.

  8. Click Add VXC to save the VXC. Repeat these steps to configure further VXCs.

  9. Click Order to proceed through the checkout process.


You can select Untag to deliver an untagged VLAN; however, this consumes the entire Megaport or MCR and prevents any other VXCs from being deployed on this Megaport or MCR.

When the VXCs are deployed, you can view them in the Portal Services page. Note that the service identifier number is the same for the VXCs at both ends of the connection.

Last update: