Creating an MCR
This topic describes how to create a Megaport Cloud RouterA managed virtual router service that establishes Layer 3 connectivity on the worldwide Megaport software-defined network (SDN).
(MCR). The Megaport ONE Portal steps you through selecting a location, specifying MCR configuration details, and placing the order.
Before you begin, you need to set up your Megaport ONE 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 ONE Account.
To create an MCR
- In the Megaport ONE Portal, choose Networking > Services.
Click Create and select MCR.
An MCR is physically homed to a core location. Select the preferred data center location for the MCR.
You can search for a data center using the Country drop-down list, or enter a search term to filter results as you type. Click Clear Filters to reset the filters. Note that you can only deploy an MCR in a billing market you have already enabled.
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.
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.
Specify the autonomous system number (ASN) of this MCR, or use the default public ASN, 133937, supplied by Megaport ONE.
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.
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.
Specify an optional 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.
Select No Minimum Term to pay-as-you-go, or select a term of 12, 24, or 36 months.
Longer terms result in a lower monthly rate. By default, a 12-month term is selected.
Partner and partner managed accounts cannot view or change MCR contract terms.
For details on contract terms, see MCR Pricing and Contract Terms.
Enter an optional promotional code and click Add Code.
Review the Global Services Agreement, then click Deploy Cloud Router to view the Summary screen.
The monthly rate is based on location and rate limit. Some partner managed accounts do not display the pricing details.
Click Confirm to place the order.
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 through a private VXC. For details on adding VXCs, see Creating a VXC.