Creating an MCR

This topic describes how to create a Megaport Cloud Router (MCR). The Megaport Portal steps you through selecting a location, specifying MCR configuration details, and placing the order.

Before you begin, you need to set up your portal account. You’ll only be able to create MCR instances in billing markets you are registered in. For details, see Setting Up a Megaport Account.

Play video    Watch a 3-minute video on the MCR creation process.

To create an MCR

  1. In the Megaport Portal, go to the Services page.
  2. Click Create MCR.
    Create MCR button

  3. An MCR is physically homed to a Megaport core location. Select the preferred data center location for the MCR and click Next. The country you choose must be a market in which you have already registered. Select MCR location

    To search for your local market in the list, enter a country in the Country Filter or a data center detail in the Search filter.

  4. Specify the details for the MCR.
    MCR details

    • Rate Limit – Select a rate limit from the drop-down list. The MCR can scale from 1 Gbps to 10 Gbps. The rate limit is an aggregate capacity that determines the speed for all connections through the MCR. MCR bandwidth is shared between all the Cloud Service Provider (CSP) connections added to it. The rate limit is fixed for the life of the service.

    • MCR Name – Specify a name for the MCR that is easily identifiable as yours, particularly if you plan on provisioning more than one MCR. For example, gcp-aws-mcr. You can change the name later, if you like.

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

    • MCR ASN – Specify the Autonomous System Number (ASN) of this MCR, or use the default public ASN, 133937, supplied by Megaport. For most configurations, the default ASN is appropriate. The ASN is used for BGP peering sessions on any VXCs connected to this MCR. See the documentation for your cloud providers before overriding the default value. For example, some public cloud services require the use of a public ASN and Microsoft blocks an ASN value of 65515 for Azure connections.

      For details on ASN, see MCR Private Cloud Peering. For details on overriding the MCR ASN, see BGP Advanced Settings.

    • Initial BGP State – Select whether newly created BGP connections are enabled or shut down by default. Select Enabled (the default) if you want any new BGP sessions you configure to be live as soon as you save the configuration. Select Shut Down if you want any new BGP sessions you configure to be left in a shut down state when you save the configuration.

      For example, you might want to select Shut Down if you are planning to add a number of BGP sessions across your Virtual Cross Connects (VXCs) but know that you want to do some other router setup before you want them exchanging route information. When you are finished configuring your routers, you can then go into the relevant BGP sessions and enable them.

      The setting you choose here just sets the default state for the new BGP session. You can override this in the BGP setup screen. For details on overriding the BGP state for an individual connection, see Shutting down a BGP connection.

  5. Click Next to view the Summary screen.

    The monthly rate is based on location and rate limit.
    MCR summary

  6. Confirm the selected options and click Add MCR.

  7. Click Create MCR to add more MCRs in other locations.
  8. Click Order.
  9. Review the Order Services agreement, and click Order Now.

    • Click Save to save the configured MCR before placing the order.
    • Click Add Promo Code to enter a promotional code, and click Add Code.

The MCR provisioning takes approximately 59 seconds to complete.


MCR is postpaid, so if you order the instance on the 15th of January, your first invoice will be on the 1st of February, and the charge will reflect the 15th of January to the 31st of January.

Now that you’ve deployed an MCR, the next step is to 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 or connect to a service provider in the Megaport Marketplace.

Connecting a 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 each MCR.


The VXC target destination type determines the peering type. The peering type determines which routes are advertised. For details, see MCR Route Advertisement.

To connect a VXC

  1. If this is the first connection for the MCR, click the tile that matches the VXC type. The tile is a shortcut to the configuration page. Alternatively, click +Connection and select a destination type: VXC tiles

  2. Click Next.

  3. Enter the the connection name and optional invoice reference number.
  4. Enter 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.
  5. Click Next.
  6. Enter one or more IP addresses and subnet mask to configure on this interface.
    For each VXC connected to an MCR you can configure one or more interfaces, IP addresses, BGP connections, or static routes. Most VXCs will use one interface. However, you can configure multiple interfaces using a Q-in-Q connection and specifying an inner VLAN tag for each interface.
  7. Select a VLAN option:

    • Not QinQ Connection – Allows a single VLAN tag (802.1q).
    • QinQ Connection – Allows the VLAN to carry multiple or dual-stacked VLANs (802.1ad).

      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.

      After selecting QinQ Connection, 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.

  8. Enter the preferred VLAN ID for the B-End of the connection. After entering a VLAN ID, Megaport verifies that the VLAN ID is available.

  9. Click Next.

  10. Enter any details specific to the VXC type.

  11. Click Next.

  12. Review the Summary details and click Add VXC.

  13. Click Order.

  14. Click Order Now.

Last update: