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.
Watch a 3-minute video on the MCR creation process.
To create an MCR
- Log in to the Megaport Portal and choose Services.
Click Create MCR.
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.
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.
Specify the details for the MCR.
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.
Partner managed accounts can apply a Partner Deal to a service. For details, see Applying a Deal to a Service.
Service Level Reference (optional) – Specify a unique identifying number for the MCR to be used for billing purposes, such as a cost center number or a unique customer ID. The service level reference number appears for each service under the Product section of the invoice. You can also edit this field for an existing service.
A VXC associated with the MCR is not automatically updated with the MCR service level reference 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.
BGP Default State – Select whether 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.
You can override this setting for an individual connection in the BGP setup screen. For details on overriding the BGP state for an individual connection, see Shutting down a BGP connection.
Click Next to view the Summary screen.
The monthly rate is based on location and rate limit. (Note, some partner managed accounts do not display the pricing details.)
Confirm the selected options and click Add MCR.
- Click Create MCR to add more MCRs in other locations.
- Click Order.
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 place your order 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. For details on adding VXCs, see Creating a VXC.