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. Log in to the Portal and choose Services.
  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 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. Some public cloud services require the use of a public ASN. See the documentation for the cloud provider before overriding the default value.

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

  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.

Note

MCR is post paid, 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 28th of February.

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 Megaport 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.

Note

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 connection details, 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. The following options are available for individual configuration for each C-Tag if you configure the VXC as Q-in-Q capable.

      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.
    Leave blank to have Megaport automatically assign the VLAN ID. 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.

Configuring a VXC

For each VXC enabled with Q-in-Q and connected to an MCR you can configure one or more interfaces, IP addresses, BGP connections, or static routes.

To configure a VXC interface

  1. Select the connection and select the A-End or the B-End.
  2. Select an 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. The following options are available for individual configuration for each C-Tag if you configure the VXC as Q-in-Q capable.

      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.

  3. Specify the IP address and subnet mask for the interface. You can add more than one IP address. Both IPv4 and IPv6 addresses are supported. Leave this field blank to defer the IP address assignment until after the VXC is provisioned. The IP address will be used for BGP peering to a cloud provider, if BGP is enabled.

  4. Click Next.

Configuring BGP

The Border Gateway Protocol (BGP) allows dynamic route table updates from the MCR across the VXC to the port. Enable one or more BGP peers for the MCR.

To configure BGP

  1. In the New Connection page, under MCR Connection details, click +Add. The connection detail section expands. IP details

  2. Click +Add BGP Connection and specify these values:

    • Local IP - The IP address on this interface that communicates with the BGP peer. The menu is autopopulated based on the address you specified in the connection detail.

    • Peer IP - The IP address for the BGP peer. For example, if the local IP is 198.162.100.1, the peer IP address would be 198.162.100.2.

    • Peer ASN - The ASN of the target routing device that will terminate the BGP connection. The ASN range is from 1 to 4294967294.

    • BGP Auth - The shared key to authenticate the BGP peer. The shared key length is from 1 to 32 characters. A shared key is optional when creating the VXC, but is required to set up the BGP peering. You can add it after you create the VXC.

    • Description - Optionally, include a description that will help identify this connection. The minimum description length is from 1 to 100 characters.

    • BGP State - By default, BGP is enabled and the connection will actively connect to the peer. You can shut down the connection without removing it. See BGP shutdown.
      BGP details

    Note

    If you have entered multiple CIDR ranges, the IP addresses are available for selection.

    Note

    Use a CIDR calculator to ensure that all data is valid and within range.

  3. Click Add.

Configuring static routes

Static routes establish reachability to peers in place of BGP connections that provide dynamic routing. You configure static routes to provide connectivity to a customer device that doesn’t support BGP or to a target device that requires manually configured addressing and routes. With static routes, you need to manually update any topology changes, and the routes aren’t advertised between networks.

Note

This option is only supported on Q-in-Q connections.

An MCR supports up to ten static routes.

To add a static route

  1. Select the VXC.
  2. Select A-End.
  3. In the MCR Connection details page, click +Add Route.
    Static route

  4. Specify the IPv4 or IPv6 destination network address in CIDR notation.

  5. Specify the IP address of the next-hop router.
  6. Optionally, include any notes that will help identify this static route.
  7. Click Add.

Source NAT assignment

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.

Note

This option is only supported on Q-in-Q connections.

NAT assignment is optional.

For details on how MCR performs NAT to support public peering types to cloud service providers, see How the MCR performs NAT.

To enable source NAT on the interface

  1. In the MCR Connection details page, next to NAT IP Address, select an IPv4 address from the drop-down list. All packets leaving this interface will have their source NAT rewritten to this address.

  2. Click Next.
    NAT assignment

For information on the BGP BFD and MED settings, see Configuring BGP Advanced Settings.

Verifying the BGP configuration

You can view the BGP configuration status for the MCR to verify that it’s working correctly.

To view the BGP status

  1. In the Portal, click Services.
  2. Select the VXC.
  3. Click A-End or B-End.
    BGP status

Troubleshooting BGP

If the Services > MCR Connection Details page displays a status issue, verify these items:

  1. Select the VXC and select A-End. Under BGP Connections, verify that the correct local ASN is in use for the A-End service of the VXC.
  2. Verify that the correct peer IP address is in use.
  3. Verify that the correct BGP MD5 password is in use for the A-End service of the VXC.

If the BGP configuration looks correct:

  • Make sure that a BGP peer is not blocking ingress or egress from TCP port 179 (BGP) and other relevant ephemeral ports.

  • Verify that a BGP peer is not advertising more than 100 prefixes to AWS. The maximum number of advertised routes to AWS is 100. The BGP session is disabled if it exceeds the prefix limit of 100 advertised routes.

Shutting down a BGP connection

By default, BGP connections are enabled and will actively connect to the BGP peer. You can temporarily disable the BGP session without removing it. BGP shutdown provides a way to administratively shut down a BGP connection while setting up a new route, performing maintenance, and so on.

To temporarily disable a BGP connection

  1. In the MCR Connection detail page, click +Add BGP Connection.

  2. In the BGP Connection page, after BGP State, click Shut Down.

  3. Click Add.
    BGP shutdown

Note

The Shut Down button is not available while a VXC is in design mode.

Tip

You can also click Shut Down in the Connection Details page. Click Yes confirm the connection shutdown.


Last update: